Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 84b6344e1d537d2e760bc9e600afb6a9f45d904235604b5de8e64a0f0a02ccf9

Tx prefix hash: 56091d73a57526a4c37dafce152dce45b99068f18541a5450385e7b0f2d0ae9d
Tx public key: e217ae8163749d9379d8bc0fa536a378c810a6a837274b249cd78ded64d29f75
Timestamp: 1734350371 Timestamp [UCT]: 2024-12-16 11:59:31 Age [y:d:h:m:s]: 00:092:22:20:07
Block: 1176437 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66203 RingCT/type: yes/0
Extra: 01e217ae8163749d9379d8bc0fa536a378c810a6a837274b249cd78ded64d29f75021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 00629f7f5f5b5e5cc719dc104e6d7f07209fe056656cf507197b9276e6029220 0.600000000000 1662770 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1176447, "vin": [ { "gen": { "height": 1176437 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00629f7f5f5b5e5cc719dc104e6d7f07209fe056656cf507197b9276e6029220" } } ], "extra": [ 1, 226, 23, 174, 129, 99, 116, 157, 147, 121, 216, 188, 15, 165, 54, 163, 120, 200, 16, 166, 168, 55, 39, 75, 36, 156, 215, 141, 237, 100, 210, 159, 117, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8