Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c11cfe92b272e0daedf905756dc201a69bd28a40016b43549187caad099f491c

Tx prefix hash: eb7d2aeaa5cecd1ceb3546bda995616f413e1944e78a42aaf4a4ef895f3a27d9
Tx public key: a07dacaef7b21f198e9ea0161d681d1bc60083547ebac6453a4b2d0c57fc4dc0
Timestamp: 1766238986 Timestamp [UCT]: 2025-12-20 13:56:26 Age [y:d:h:m:s]: 00:001:10:49:14
Block: 1437770 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1033 RingCT/type: yes/0
Extra: 01a07dacaef7b21f198e9ea0161d681d1bc60083547ebac6453a4b2d0c57fc4dc002110000000d7b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c67a548f97806fb7929686886f0d70921cdc54205fd0c2d83eadd5514ce2c4ee 0.600000000000 1926581 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": 1437780, "vin": [ { "gen": { "height": 1437770 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c67a548f97806fb7929686886f0d70921cdc54205fd0c2d83eadd5514ce2c4ee" } } ], "extra": [ 1, 160, 125, 172, 174, 247, 178, 31, 25, 142, 158, 160, 22, 29, 104, 29, 27, 198, 0, 131, 84, 126, 186, 198, 69, 58, 75, 45, 12, 87, 252, 77, 192, 2, 17, 0, 0, 0, 13, 123, 30, 81, 172, 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