Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e22242870704823773b4c1bbac9aab383093c94b0ca05417e5fd4962fb1b231

Tx prefix hash: a43e557a64b246da405b68b1ba1e9fa5d553f9009eb44dcb2e9c9f111ffd2dcd
Tx public key: 243c57a367b191244a2bd05cc1cccc60fa879e7f48e616bacbbbddf9aa75d9ca
Timestamp: 1708861864 Timestamp [UCT]: 2024-02-25 11:51:04 Age [y:d:h:m:s]: 01:300:02:48:40
Block: 965221 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 473283 RingCT/type: yes/0
Extra: 01243c57a367b191244a2bd05cc1cccc60fa879e7f48e616bacbbbddf9aa75d9ca0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ba9bdf9b05f37cedd1af6ae79510afb561d01e75519be17d7ddc7b2aa83267f5 0.600000000000 1424970 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": 965231, "vin": [ { "gen": { "height": 965221 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba9bdf9b05f37cedd1af6ae79510afb561d01e75519be17d7ddc7b2aa83267f5" } } ], "extra": [ 1, 36, 60, 87, 163, 103, 177, 145, 36, 74, 43, 208, 92, 193, 204, 204, 96, 250, 135, 158, 127, 72, 230, 22, 186, 203, 187, 221, 249, 170, 117, 217, 202, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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