Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1367285d02288a2f95b94a2307110e2d537ff7c25130a75148cc4322d17f0ae

Tx prefix hash: 07b05d12de566040c9b819e37b69906598b24096c12057fb35c98987eecd25c6
Tx public key: 0260ea5cfb2c3c477e86dc801eb39d02c754f72c7e0e441b13aa927d4f152fdc
Timestamp: 1745713037 Timestamp [UCT]: 2025-04-27 00:17:17 Age [y:d:h:m:s]: 00:207:07:44:12
Block: 1270211 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145895 RingCT/type: yes/0
Extra: 010260ea5cfb2c3c477e86dc801eb39d02c754f72c7e0e441b13aa927d4f152fdc0211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 058bccb4313cdf68552bb6bc182f6c2725e3897cd5527af186d0f182dbfff167 0.600000000000 1757452 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": 1270221, "vin": [ { "gen": { "height": 1270211 } } ], "vout": [ { "amount": 600000000, "target": { "key": "058bccb4313cdf68552bb6bc182f6c2725e3897cd5527af186d0f182dbfff167" } } ], "extra": [ 1, 2, 96, 234, 92, 251, 44, 60, 71, 126, 134, 220, 128, 30, 179, 157, 2, 199, 84, 247, 44, 126, 14, 68, 27, 19, 170, 146, 125, 79, 21, 47, 220, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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