Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65a625b9d055b11f678a8afafc4be6b6045ca6daf2a495a74190d252e30f32c6

Tx prefix hash: e57e5d6f4bac22dc4d03f2afc66058cc22f4749984ff97d376c10fc1134fb214
Tx public key: 6861e901e3c0d4c2877f059946001cd01c23c48974ea3624ea5b981d22b9dbd1
Timestamp: 1703995110 Timestamp [UCT]: 2023-12-31 03:58:30 Age [y:d:h:m:s]: 01:029:20:04:53
Block: 924857 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282415 RingCT/type: yes/0
Extra: 016861e901e3c0d4c2877f059946001cd01c23c48974ea3624ea5b981d22b9dbd102110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e44ba0f047086d05a9bc350c443fc3438bbbc4e2322a57d4b21d8c097c458afa 0.600000000000 1382617 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": 924867, "vin": [ { "gen": { "height": 924857 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e44ba0f047086d05a9bc350c443fc3438bbbc4e2322a57d4b21d8c097c458afa" } } ], "extra": [ 1, 104, 97, 233, 1, 227, 192, 212, 194, 135, 127, 5, 153, 70, 0, 28, 208, 28, 35, 196, 137, 116, 234, 54, 36, 234, 91, 152, 29, 34, 185, 219, 209, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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