Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 487e3d77bfe59b95b9895ad8e1ee809ed1497ef3a80cae50dadc73a3844281ae

Tx prefix hash: 2457d456dac793dc529b9692db5f96d229eb72d3a063cac5b782ea080949977e
Tx public key: d9ff076763d8f2f31a0d147955a9fb952007c28ed4a9b138a0050fe728c42af7
Timestamp: 1723179123 Timestamp [UCT]: 2024-08-09 04:52:03 Age [y:d:h:m:s]: 00:145:14:32:21
Block: 1083914 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104161 RingCT/type: yes/0
Extra: 01d9ff076763d8f2f31a0d147955a9fb952007c28ed4a9b138a0050fe728c42af702110000000d91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2eb33e6545766122811efa044d8a68c24a1c59fb2f6632b2aac9a1e03d0cf03 0.600000000000 1557997 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": 1083924, "vin": [ { "gen": { "height": 1083914 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2eb33e6545766122811efa044d8a68c24a1c59fb2f6632b2aac9a1e03d0cf03" } } ], "extra": [ 1, 217, 255, 7, 103, 99, 216, 242, 243, 26, 13, 20, 121, 85, 169, 251, 149, 32, 7, 194, 142, 212, 169, 177, 56, 160, 5, 15, 231, 40, 196, 42, 247, 2, 17, 0, 0, 0, 13, 145, 225, 60, 4, 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