Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a0816351c45785ab53c6352678fdd823f1c6ddbc5fc5fb3276c918ad3e86937

Tx prefix hash: abb683415f16dc1fc779ef9657f3bb9a7806663a1bc7a1654c5897d8d9cf61cd
Tx public key: efeb8c5732f499397e06c93639fbc7e73ac2f9692f79f6e449ee8e1d9c9a0e84
Timestamp: 1710033053 Timestamp [UCT]: 2024-03-10 01:10:53 Age [y:d:h:m:s]: 00:250:10:49:43
Block: 974934 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179293 RingCT/type: yes/0
Extra: 01efeb8c5732f499397e06c93639fbc7e73ac2f9692f79f6e449ee8e1d9c9a0e8402110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2df59551fcf10a22b9e739b95459ec80394b7d6ef38a15af9cec06889c4da5ca 0.600000000000 1434901 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": 974944, "vin": [ { "gen": { "height": 974934 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2df59551fcf10a22b9e739b95459ec80394b7d6ef38a15af9cec06889c4da5ca" } } ], "extra": [ 1, 239, 235, 140, 87, 50, 244, 153, 57, 126, 6, 201, 54, 57, 251, 199, 231, 58, 194, 249, 105, 47, 121, 246, 228, 73, 238, 142, 29, 156, 154, 14, 132, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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