Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f0b0b1afb1162216172cf94c97634746d61c6a49667605677354cb3030fc03f

Tx prefix hash: f8e1ad043e4a067012e6117fefcc18fd65b4709ee9ca349a7e10a0ce94b307ee
Tx public key: 38b860d3f6c938d3de73abe339e1f4be73f81cca71d2ecfe677325d1de8765b7
Timestamp: 1703414672 Timestamp [UCT]: 2023-12-24 10:44:32 Age [y:d:h:m:s]: 01:322:17:02:31
Block: 920059 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 489477 RingCT/type: yes/0
Extra: 0138b860d3f6c938d3de73abe339e1f4be73f81cca71d2ecfe677325d1de8765b70211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 93764fbc3a2b1b947da3ba9a77670ac33e61d586fae4491d4cb4edeec24a2f6e 0.600000000000 1377737 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": 920069, "vin": [ { "gen": { "height": 920059 } } ], "vout": [ { "amount": 600000000, "target": { "key": "93764fbc3a2b1b947da3ba9a77670ac33e61d586fae4491d4cb4edeec24a2f6e" } } ], "extra": [ 1, 56, 184, 96, 211, 246, 201, 56, 211, 222, 115, 171, 227, 57, 225, 244, 190, 115, 248, 28, 202, 113, 210, 236, 254, 103, 115, 37, 209, 222, 135, 101, 183, 2, 17, 0, 0, 0, 5, 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