Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43bfea4601434d0d1539dc5e99febdd3c9da8f2755afcc974f929fae0ea942cc

Tx prefix hash: 7ef16ba1325f90107fe415f21d2ea25bae5f1b9dfec578ff8e623305d3ff9841
Tx public key: 70f4d34620aaaa98a03436ff9fdf8efed3e86ce39088d4e6f3beb1de985f4635
Timestamp: 1682375508 Timestamp [UCT]: 2023-04-24 22:31:48 Age [y:d:h:m:s]: 02:031:20:25:30
Block: 745884 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 544923 RingCT/type: yes/0
Extra: 0170f4d34620aaaa98a03436ff9fdf8efed3e86ce39088d4e6f3beb1de985f463502110000000675e3f0e9000000000000000000

1 output(s) for total of 2.072893005000 dcy

stealth address amount amount idx
00: f868395a334c54401be6e75bbaa2483ee9be513360b3396ea3287e3172b8ab05 2.072893005000 1193377 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": 745894, "vin": [ { "gen": { "height": 745884 } } ], "vout": [ { "amount": 2072893005, "target": { "key": "f868395a334c54401be6e75bbaa2483ee9be513360b3396ea3287e3172b8ab05" } } ], "extra": [ 1, 112, 244, 211, 70, 32, 170, 170, 152, 160, 52, 54, 255, 159, 223, 142, 254, 211, 232, 108, 227, 144, 136, 212, 230, 243, 190, 177, 222, 152, 95, 70, 53, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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