Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e8b52facdfcaa09e433cc574189b06826d38e74f47ab8cd74ec38788f7bd0d2

Tx prefix hash: 78a248d8a5a9ce7e8b91ab3df4c47bc4275485055bb2d479897fa24a0efdf68e
Tx public key: 6fdc6bd227a87756cce3c9dc0169dec140e8daa08d26c9bfc7569055b4f6ee9e
Timestamp: 1702627916 Timestamp [UCT]: 2023-12-15 08:11:56 Age [y:d:h:m:s]: 01:124:17:46:21
Block: 913525 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 350292 RingCT/type: yes/0
Extra: 016fdc6bd227a87756cce3c9dc0169dec140e8daa08d26c9bfc7569055b4f6ee9e02110000000633af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e30be7a708924007f9e670b8014a2f02e0955c074e3ebef878cb73664cebbd7b 0.600000000000 1370797 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": 913535, "vin": [ { "gen": { "height": 913525 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e30be7a708924007f9e670b8014a2f02e0955c074e3ebef878cb73664cebbd7b" } } ], "extra": [ 1, 111, 220, 107, 210, 39, 168, 119, 86, 204, 227, 201, 220, 1, 105, 222, 193, 64, 232, 218, 160, 141, 38, 201, 191, 199, 86, 144, 85, 180, 246, 238, 158, 2, 17, 0, 0, 0, 6, 51, 175, 153, 244, 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