Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5535c2bfa9be9a0be7736ce530abc16bb0b95b0ce74b166610f22064d0a419d4

Tx prefix hash: c4d84315d350cdd440981319a0375786ff954a5d53b2eb6fb6f501e5c58cf6f2
Tx public key: f300e19a1f28c72f76c74963d26aacf76c150bf6bb2189f0f815193606417e7d
Timestamp: 1711316323 Timestamp [UCT]: 2024-03-24 21:38:43 Age [y:d:h:m:s]: 01:050:14:50:01
Block: 985584 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297160 RingCT/type: yes/0
Extra: 01f300e19a1f28c72f76c74963d26aacf76c150bf6bb2189f0f815193606417e7d0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4fdc5ca05cf8177395fd49d21ef2592338aea58fe9b05ca2f28b52f728a64191 0.600000000000 1445801 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": 985594, "vin": [ { "gen": { "height": 985584 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4fdc5ca05cf8177395fd49d21ef2592338aea58fe9b05ca2f28b52f728a64191" } } ], "extra": [ 1, 243, 0, 225, 154, 31, 40, 199, 47, 118, 199, 73, 99, 210, 106, 172, 247, 108, 21, 11, 246, 187, 33, 137, 240, 248, 21, 25, 54, 6, 65, 126, 125, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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