Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05694c53add82b0a41e08204a16196dea5168609b4ddb92c967971ebb16ca534

Tx prefix hash: d20191d38d02e8084a733b36c8f7479d47892bf6097018b5c1a2403db20c3a32
Tx public key: d8f92362c0e950689d75535374d7f2ed8d97b19ead797bc5a3955d12b20b5b07
Timestamp: 1726289620 Timestamp [UCT]: 2024-09-14 04:53:40 Age [y:d:h:m:s]: 00:117:22:52:06
Block: 1109695 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84348 RingCT/type: yes/0
Extra: 01d8f92362c0e950689d75535374d7f2ed8d97b19ead797bc5a3955d12b20b5b0702110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 314e9e72fef77115912ba16cb3d8d8455d27ffdc77d329d4a1ced918928fb2c2 0.600000000000 1588042 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": 1109705, "vin": [ { "gen": { "height": 1109695 } } ], "vout": [ { "amount": 600000000, "target": { "key": "314e9e72fef77115912ba16cb3d8d8455d27ffdc77d329d4a1ced918928fb2c2" } } ], "extra": [ 1, 216, 249, 35, 98, 192, 233, 80, 104, 157, 117, 83, 83, 116, 215, 242, 237, 141, 151, 177, 158, 173, 121, 123, 197, 163, 149, 93, 18, 178, 11, 91, 7, 2, 17, 0, 0, 0, 6, 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