Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5745bc20e2f57953f439b3ff81b98023eb4ffb2b4d25b37d8d33eb642d4f0269

Tx prefix hash: c0d064a15813fc2052da2fdab2cfb4c5854b176a8c866a6094006e24a4c3d2d3
Tx public key: 20cd6b4451ec5c66a74f86e3b06b3dfd7c25beda9ad9849ca5c613f25e7988da
Timestamp: 1726452835 Timestamp [UCT]: 2024-09-16 02:13:55 Age [y:d:h:m:s]: 00:182:02:40:46
Block: 1111050 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129987 RingCT/type: yes/0
Extra: 0120cd6b4451ec5c66a74f86e3b06b3dfd7c25beda9ad9849ca5c613f25e7988da021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c2b029bc1302f0f5bd01258d73b0eb49bc6218d443e04880d661b43570367e2 0.600000000000 1589875 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": 1111060, "vin": [ { "gen": { "height": 1111050 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c2b029bc1302f0f5bd01258d73b0eb49bc6218d443e04880d661b43570367e2" } } ], "extra": [ 1, 32, 205, 107, 68, 81, 236, 92, 102, 167, 79, 134, 227, 176, 107, 61, 253, 124, 37, 190, 218, 154, 217, 132, 156, 165, 198, 19, 242, 94, 121, 136, 218, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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