Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52017e6f071a2d71fd2028748b228061d64d26c9204fb17452d7c118c61be786

Tx prefix hash: 9cbee403016f365623163c7d56180fdd705dc4ef74cc78308f19ce23ad5b0733
Tx public key: 329836dc91e778da00a3bda8a1e3c06dd0f6fd4be2b64ab1087d22beb423e8d6
Timestamp: 1705419034 Timestamp [UCT]: 2024-01-16 15:30:34 Age [y:d:h:m:s]: 01:299:00:38:26
Block: 936656 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 472541 RingCT/type: yes/0
Extra: 01329836dc91e778da00a3bda8a1e3c06dd0f6fd4be2b64ab1087d22beb423e8d60211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2a314f53061a0212b23d945b401327ea735eba16aa680e96b7dfa45f7226f463 0.600000000000 1394694 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": 936666, "vin": [ { "gen": { "height": 936656 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a314f53061a0212b23d945b401327ea735eba16aa680e96b7dfa45f7226f463" } } ], "extra": [ 1, 50, 152, 54, 220, 145, 231, 120, 218, 0, 163, 189, 168, 161, 227, 192, 109, 208, 246, 253, 75, 226, 182, 74, 177, 8, 125, 34, 190, 180, 35, 232, 214, 2, 17, 0, 0, 0, 7, 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