Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71ad61a2153c77f51118949d864ec8249fc3f246a428d1f82eeb1da1632d1249

Tx prefix hash: 13f04a9d1a49f3aebb1def84e347effd11b3f5a7a68b033e7045e239c3947939
Tx public key: c32eadd833345c7df0cc2d7b59b836d2fae543faf8f800a29ca03339ca2a9274
Timestamp: 1709229345 Timestamp [UCT]: 2024-02-29 17:55:45 Age [y:d:h:m:s]: 01:025:17:40:03
Block: 968269 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279375 RingCT/type: yes/0
Extra: 01c32eadd833345c7df0cc2d7b59b836d2fae543faf8f800a29ca03339ca2a92740211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 94f3893b4af89d333019746bf26441119688cfd7e4e2e8070c0e7b1d7b2653d9 0.600000000000 1428076 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": 968279, "vin": [ { "gen": { "height": 968269 } } ], "vout": [ { "amount": 600000000, "target": { "key": "94f3893b4af89d333019746bf26441119688cfd7e4e2e8070c0e7b1d7b2653d9" } } ], "extra": [ 1, 195, 46, 173, 216, 51, 52, 92, 125, 240, 204, 45, 123, 89, 184, 54, 210, 250, 229, 67, 250, 248, 248, 0, 162, 156, 160, 51, 57, 202, 42, 146, 116, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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