Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2293a8a92984b959e1be1503ccca88a7c830afede1c04edd860a92bde8eecf4

Tx prefix hash: a61091b21be5b243136fbc6e2a7bfc74478bd6460e9916bc9988a7ccce121313
Tx public key: 9c03472c4bb811060ebf311f4617fae8aa11216252202c04c2dd6f60f6c06410
Timestamp: 1707867211 Timestamp [UCT]: 2024-02-13 23:33:31 Age [y:d:h:m:s]: 01:052:17:10:51
Block: 956966 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298705 RingCT/type: yes/0
Extra: 019c03472c4bb811060ebf311f4617fae8aa11216252202c04c2dd6f60f6c064100211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6dd751c063fb56889d34b4b99ba758b5eca15ce4920cb777c3e6129270fc3e6d 0.600000000000 1416280 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": 956976, "vin": [ { "gen": { "height": 956966 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6dd751c063fb56889d34b4b99ba758b5eca15ce4920cb777c3e6129270fc3e6d" } } ], "extra": [ 1, 156, 3, 71, 44, 75, 184, 17, 6, 14, 191, 49, 31, 70, 23, 250, 232, 170, 17, 33, 98, 82, 32, 44, 4, 194, 221, 111, 96, 246, 192, 100, 16, 2, 17, 0, 0, 0, 4, 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