Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 840ad55076fded01123a86ea64e82541305182d2cc4020fdeee49ffd4e1862ec

Tx prefix hash: 8b8815cf70b1a9d9718e50992240c4c0c7a1c8cac8efa8a111d7fda947876d0d
Tx public key: fab457e72f258c52ca578449dcdf07c6dbe83d54fd856b781826e33116dbb265
Timestamp: 1721365359 Timestamp [UCT]: 2024-07-19 05:02:39 Age [y:d:h:m:s]: 00:247:21:11:41
Block: 1068884 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177060 RingCT/type: yes/0
Extra: 01fab457e72f258c52ca578449dcdf07c6dbe83d54fd856b781826e33116dbb26502110000001191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a97e16c401cb7fd2e9a0dbd9b3cb05627be4015fb09f569f291cea7e523e120b 0.600000000000 1540089 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": 1068894, "vin": [ { "gen": { "height": 1068884 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a97e16c401cb7fd2e9a0dbd9b3cb05627be4015fb09f569f291cea7e523e120b" } } ], "extra": [ 1, 250, 180, 87, 231, 47, 37, 140, 82, 202, 87, 132, 73, 220, 223, 7, 198, 219, 232, 61, 84, 253, 133, 107, 120, 24, 38, 227, 49, 22, 219, 178, 101, 2, 17, 0, 0, 0, 17, 145, 225, 60, 4, 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