Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdc812bb241a8a04cae6530ca3618d0a7306053fe12b2b9c4a448a123169efab

Tx prefix hash: 43c9c79a83eec5ac43d3f3e708c2ee877e87420edbb98852eb49a63e5c95db7d
Tx public key: 358318051bddaa28d8d34077fbe6573104acc2ada1f9cfa583146c2d8a23998f
Timestamp: 1693933138 Timestamp [UCT]: 2023-09-05 16:58:58 Age [y:d:h:m:s]: 01:217:05:03:44
Block: 841630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 416352 RingCT/type: yes/0
Extra: 01358318051bddaa28d8d34077fbe6573104acc2ada1f9cfa583146c2d8a23998f02110000000775e3f0e9000000000000000000

1 output(s) for total of 0.998459611000 dcy

stealth address amount amount idx
00: f732d714751826df0443d0de16b062d54204e9a9c2b1e423697f76692215f16b 0.998459611000 1294678 of 0

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": 841640, "vin": [ { "gen": { "height": 841630 } } ], "vout": [ { "amount": 998459611, "target": { "key": "f732d714751826df0443d0de16b062d54204e9a9c2b1e423697f76692215f16b" } } ], "extra": [ 1, 53, 131, 24, 5, 27, 221, 170, 40, 216, 211, 64, 119, 251, 230, 87, 49, 4, 172, 194, 173, 161, 249, 207, 165, 131, 20, 108, 45, 138, 35, 153, 143, 2, 17, 0, 0, 0, 7, 117, 227, 240, 233, 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