Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a14cb4f24496aad2f6cb2e17cdb2c79cec7ccf9524ad0e39f6f0abbef3791b6e

Tx prefix hash: a1c7795ed4e44e4cdc393a9de5a18021a3f280302c0e9414b31c02920b7ba0a7
Tx public key: a7a4f468b2069802b509b1a7b40be39fb42dcfae1cad0fe886ca5ac25b084520
Timestamp: 1729837252 Timestamp [UCT]: 2024-10-25 06:20:52 Age [y:d:h:m:s]: 00:165:20:13:28
Block: 1139074 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118326 RingCT/type: yes/0
Extra: 01a7a4f468b2069802b509b1a7b40be39fb42dcfae1cad0fe886ca5ac25b08452002110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f478ca1cee711b24375125b276105381884f613419bbcd97abd9fbbc2aab9003 0.600000000000 1622833 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": 1139084, "vin": [ { "gen": { "height": 1139074 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f478ca1cee711b24375125b276105381884f613419bbcd97abd9fbbc2aab9003" } } ], "extra": [ 1, 167, 164, 244, 104, 178, 6, 152, 2, 181, 9, 177, 167, 180, 11, 227, 159, 180, 45, 207, 174, 28, 173, 15, 232, 134, 202, 90, 194, 91, 8, 69, 32, 2, 17, 0, 0, 0, 10, 0, 127, 151, 138, 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