Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1facc13ad5bf32a03c4db34f67d9fdf58dc9bcf4bfb59dfc363b980637e26301

Tx prefix hash: 53b9887546d7ed3b1a419874249c4ce1dacd5b8c577f5ca575cd1136d4c83927
Tx public key: 31316414de2144b1281d9ac959e3abee6a1f090b1fdafe10d4b18b8f5a63962c
Timestamp: 1704434656 Timestamp [UCT]: 2024-01-05 06:04:16 Age [y:d:h:m:s]: 01:308:15:32:05
Block: 928488 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 479431 RingCT/type: yes/0
Extra: 0131316414de2144b1281d9ac959e3abee6a1f090b1fdafe10d4b18b8f5a63962c02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f44d94afa525d08723b6809f36c694ccce75397b846be50f2679c43b462bf9f 0.600000000000 1386348 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": 928498, "vin": [ { "gen": { "height": 928488 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f44d94afa525d08723b6809f36c694ccce75397b846be50f2679c43b462bf9f" } } ], "extra": [ 1, 49, 49, 100, 20, 222, 33, 68, 177, 40, 29, 154, 201, 89, 227, 171, 238, 106, 31, 9, 11, 31, 218, 254, 16, 212, 177, 139, 143, 90, 99, 150, 44, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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