Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5fcc3fde85a8d206c8b5252b75dc9cbdd3a3c9a62fcd652a9dce92028746a375

Tx prefix hash: a196668d189aacaa88b590bbb02235697fb9abd546e9b0497c8d14936dd3f1d5
Tx public key: 0e4a95e2884aa24b4deeaab5d7b630a1f410ca4c468466ae7326158cc8c66bac
Timestamp: 1726945448 Timestamp [UCT]: 2024-09-21 19:04:08 Age [y:d:h:m:s]: 00:233:23:09:43
Block: 1115133 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167066 RingCT/type: yes/0
Extra: 010e4a95e2884aa24b4deeaab5d7b630a1f410ca4c468466ae7326158cc8c66bac02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b2984319cadf908082148a8384458cb9a9e2f4a394296c578cb67d859406f98 0.600000000000 1595160 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": 1115143, "vin": [ { "gen": { "height": 1115133 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b2984319cadf908082148a8384458cb9a9e2f4a394296c578cb67d859406f98" } } ], "extra": [ 1, 14, 74, 149, 226, 136, 74, 162, 75, 77, 238, 170, 181, 215, 182, 48, 161, 244, 16, 202, 76, 70, 132, 102, 174, 115, 38, 21, 140, 200, 198, 107, 172, 2, 17, 0, 0, 0, 2, 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