Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d30d0506be0585be657ea2ac533fb386f36ba083e3536fe61f3d43e6561ebb68

Tx prefix hash: 2f8468a4d0a16bb3fe35cb1376b84334ee3a14818c622da98c49e09e918eae0c
Tx public key: 25d6c9c9b7692b12701df7c7ce4b0a124283aa5531a45456a42cb87b52ecaa43
Timestamp: 1705008614 Timestamp [UCT]: 2024-01-11 21:30:14 Age [y:d:h:m:s]: 01:142:20:55:37
Block: 933252 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363264 RingCT/type: yes/0
Extra: 0125d6c9c9b7692b12701df7c7ce4b0a124283aa5531a45456a42cb87b52ecaa4302110000000b7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0616bf339efec945894b3482db436ffa2b0588f07263ddc65e4cdc22ded7e5b2 0.600000000000 1391212 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": 933262, "vin": [ { "gen": { "height": 933252 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0616bf339efec945894b3482db436ffa2b0588f07263ddc65e4cdc22ded7e5b2" } } ], "extra": [ 1, 37, 214, 201, 201, 183, 105, 43, 18, 112, 29, 247, 199, 206, 75, 10, 18, 66, 131, 170, 85, 49, 164, 84, 86, 164, 44, 184, 123, 82, 236, 170, 67, 2, 17, 0, 0, 0, 11, 122, 156, 244, 199, 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