Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1148244c5fe45c9f5f56a92c5d8f650ffd53f50655d75c90fde2582037f41555

Tx prefix hash: 2b63e85e8c5eb5e4c3dba741eb9980aff5532932d49e802f27de8cf74fc2f3c7
Tx public key: 4053199f90d19218fb4f3627a21a423df789efbaa6c057ebadd318d48eeb46e5
Timestamp: 1701951137 Timestamp [UCT]: 2023-12-07 12:12:17 Age [y:d:h:m:s]: 01:154:04:09:33
Block: 907915 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371357 RingCT/type: yes/0
Extra: 014053199f90d19218fb4f3627a21a423df789efbaa6c057ebadd318d48eeb46e502110000000675e3f0e9000000000000000000

1 output(s) for total of 0.602144444000 dcy

stealth address amount amount idx
00: e8e38cdd7c793cf3dc1c49cb0cca2d2254f47dafca155a1f6e9a0bd3fedfc3c9 0.602144444000 1364912 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": 907925, "vin": [ { "gen": { "height": 907915 } } ], "vout": [ { "amount": 602144444, "target": { "key": "e8e38cdd7c793cf3dc1c49cb0cca2d2254f47dafca155a1f6e9a0bd3fedfc3c9" } } ], "extra": [ 1, 64, 83, 25, 159, 144, 209, 146, 24, 251, 79, 54, 39, 162, 26, 66, 61, 247, 137, 239, 186, 166, 192, 87, 235, 173, 211, 24, 212, 142, 235, 70, 229, 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