Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3e94530c9cae5309f37afb75c77f8ae5d9c463258ff335980058a4353870e77

Tx prefix hash: 3f290cafedd58048c50fb7a4cb43aedd6e9d652ae23f19979a45590c106a9336
Tx public key: 6984f01cd476de29aef354f6cfbd0e2c63ab0fd89582c6a8cc6ef8a59628d934
Timestamp: 1713722322 Timestamp [UCT]: 2024-04-21 17:58:42 Age [y:d:h:m:s]: 00:308:04:35:41
Block: 1005501 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220302 RingCT/type: yes/0
Extra: 016984f01cd476de29aef354f6cfbd0e2c63ab0fd89582c6a8cc6ef8a59628d9340211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e10cf033acb208166e8178b96a67e27917beef0c305ceb18fe8c0638d84dfaf5 0.600000000000 1466219 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": 1005511, "vin": [ { "gen": { "height": 1005501 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e10cf033acb208166e8178b96a67e27917beef0c305ceb18fe8c0638d84dfaf5" } } ], "extra": [ 1, 105, 132, 240, 28, 212, 118, 222, 41, 174, 243, 84, 246, 207, 189, 14, 44, 99, 171, 15, 216, 149, 130, 198, 168, 204, 110, 248, 165, 150, 40, 217, 52, 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