Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: efbb3c20889f2734f1b5e1c1703d7c545208d53af6bd5da66e76c214169a6067

Tx prefix hash: c001b6df3dbab2237dff56823aa7489835c91ddb4c2d36a4cdc533725b37e302
Tx public key: 25b8b017fe3c0ce07f467809a30fe1fa6d9833f9159c65a83a51fb37bef90dee
Timestamp: 1725526997 Timestamp [UCT]: 2024-09-05 09:03:17 Age [y:d:h:m:s]: 01:064:17:54:38
Block: 1103376 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304698 RingCT/type: yes/0
Extra: 0125b8b017fe3c0ce07f467809a30fe1fa6d9833f9159c65a83a51fb37bef90dee021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5123c1faf777feade255ca639ea9cf0b2acd7250940501dc71f20132668ca1a3 0.600000000000 1580183 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": 1103386, "vin": [ { "gen": { "height": 1103376 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5123c1faf777feade255ca639ea9cf0b2acd7250940501dc71f20132668ca1a3" } } ], "extra": [ 1, 37, 184, 176, 23, 254, 60, 12, 224, 127, 70, 120, 9, 163, 15, 225, 250, 109, 152, 51, 249, 21, 156, 101, 168, 58, 81, 251, 55, 190, 249, 13, 238, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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