Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c79246f3d0e656d47a34d0328952f294de7bffb9e9b957ee16de19143088b2a

Tx prefix hash: af01c97b035d6998419b6c992027f128135e7ddc2b2f2003a8522485b7e5ea72
Tx public key: 393c7abb00bb5f1b30364f5f4ace33a8ddd3238a12c2482d12fd9f75909008ee
Timestamp: 1719538542 Timestamp [UCT]: 2024-06-28 01:35:42 Age [y:d:h:m:s]: 00:286:01:50:03
Block: 1053727 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204422 RingCT/type: yes/0
Extra: 01393c7abb00bb5f1b30364f5f4ace33a8ddd3238a12c2482d12fd9f75909008ee0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2a804d48fa465a71c4ddde165fb0c08329987c7e10684781454bd968adaf90dd 0.600000000000 1524076 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": 1053737, "vin": [ { "gen": { "height": 1053727 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a804d48fa465a71c4ddde165fb0c08329987c7e10684781454bd968adaf90dd" } } ], "extra": [ 1, 57, 60, 122, 187, 0, 187, 95, 27, 48, 54, 79, 95, 74, 206, 51, 168, 221, 211, 35, 138, 18, 194, 72, 45, 18, 253, 159, 117, 144, 144, 8, 238, 2, 17, 0, 0, 0, 2, 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