Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b500cc9043cace2303cf0c6926b6e8bc03a398d80d9dfddd7eaad8241698d052

Tx prefix hash: 02a1db917016557cf5b6013bfbd39a62093bcd7a6de3069fc016cbf8e9559e24
Tx public key: 0461f1e5c33de7f1c821e4084d870f1ce07ee762fb47140e3ba2975b0bfad2c7
Timestamp: 1740602863 Timestamp [UCT]: 2025-02-26 20:47:43 Age [y:d:h:m:s]: 00:267:10:57:22
Block: 1227898 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188902 RingCT/type: yes/0
Extra: 010461f1e5c33de7f1c821e4084d870f1ce07ee762fb47140e3ba2975b0bfad2c70211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5462eb4e94c25228a5dd8efb9fd3fd80b4d6d95d6071f32058d1a1da4a86cbfe 0.600000000000 1714773 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": 1227908, "vin": [ { "gen": { "height": 1227898 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5462eb4e94c25228a5dd8efb9fd3fd80b4d6d95d6071f32058d1a1da4a86cbfe" } } ], "extra": [ 1, 4, 97, 241, 229, 195, 61, 231, 241, 200, 33, 228, 8, 77, 135, 15, 28, 224, 126, 231, 98, 251, 71, 20, 14, 59, 162, 151, 91, 11, 250, 210, 199, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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