Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b897a5c2bf3b90146acebd7dfdbf01a1ebf4c6727a9d1784897c7c0372bab62

Tx prefix hash: 51f128962c25e83c82328571060cde812af245752fec852fac3fb3866d9611b1
Tx public key: 229fd0c1543dc37077d5b247d7a4642ee5e444de795f12499036221dc71c0dce
Timestamp: 1695357691 Timestamp [UCT]: 2023-09-22 04:41:31 Age [y:d:h:m:s]: 01:200:01:07:47
Block: 853451 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 404044 RingCT/type: yes/0
Extra: 01229fd0c1543dc37077d5b247d7a4642ee5e444de795f12499036221dc71c0dce02110000000233af99f4000000000000000000

1 output(s) for total of 0.912352369000 dcy

stealth address amount amount idx
00: dcda50e410e0747cec3369efe81ffd0711824a5b3dceb64ce94dca05f4d8d6a7 0.912352369000 1307357 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": 853461, "vin": [ { "gen": { "height": 853451 } } ], "vout": [ { "amount": 912352369, "target": { "key": "dcda50e410e0747cec3369efe81ffd0711824a5b3dceb64ce94dca05f4d8d6a7" } } ], "extra": [ 1, 34, 159, 208, 193, 84, 61, 195, 112, 119, 213, 178, 71, 215, 164, 100, 46, 229, 228, 68, 222, 121, 95, 18, 73, 144, 54, 34, 29, 199, 28, 13, 206, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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