Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f63a6ea22803caf1d7ea53ee0db2872f4617dd5725a7b3dbfd37476543189d9

Tx prefix hash: 5a18d1ae2cf230ce78f717da14b3ec252009e5a4baa93314bb62b5bc0ec7151f
Tx public key: 5c7bb348b5c01fcb020c3c7e96e12ac9efb28d9f4ec537bb51a293260a259a73
Timestamp: 1725140413 Timestamp [UCT]: 2024-08-31 21:40:13 Age [y:d:h:m:s]: 00:220:20:48:54
Block: 1100170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157705 RingCT/type: yes/0
Extra: 015c7bb348b5c01fcb020c3c7e96e12ac9efb28d9f4ec537bb51a293260a259a7302110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 893671480f80b0042f1efe345b021ff377dc33c085969b0a5939e713c3bbaac6 0.600000000000 1576143 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": 1100180, "vin": [ { "gen": { "height": 1100170 } } ], "vout": [ { "amount": 600000000, "target": { "key": "893671480f80b0042f1efe345b021ff377dc33c085969b0a5939e713c3bbaac6" } } ], "extra": [ 1, 92, 123, 179, 72, 181, 192, 31, 203, 2, 12, 60, 126, 150, 225, 42, 201, 239, 178, 141, 159, 78, 197, 55, 187, 81, 162, 147, 38, 10, 37, 154, 115, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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