Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4403ff9bc7daf404324560032c99996f5d3b1b2853c6707c309c491557b656f7

Tx prefix hash: 7823c627be5b8c244afb3397df6a54c77a2c8835daafb1b42088b8b32ba079b3
Tx public key: 60d86e45b9ba3d6c6fbdfe84b66df5f3ffd6d1063ac701f917a2a51e6af421ab
Timestamp: 1702683302 Timestamp [UCT]: 2023-12-15 23:35:02 Age [y:d:h:m:s]: 01:110:02:51:24
Block: 913984 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339830 RingCT/type: yes/0
Extra: 0160d86e45b9ba3d6c6fbdfe84b66df5f3ffd6d1063ac701f917a2a51e6af421ab021100000001faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 744135363e0c454c4d6c40e230017a5049422c241e8e6b135c275d2f2d8f2a05 0.600000000000 1371264 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": 913994, "vin": [ { "gen": { "height": 913984 } } ], "vout": [ { "amount": 600000000, "target": { "key": "744135363e0c454c4d6c40e230017a5049422c241e8e6b135c275d2f2d8f2a05" } } ], "extra": [ 1, 96, 216, 110, 69, 185, 186, 61, 108, 111, 189, 254, 132, 182, 109, 245, 243, 255, 214, 209, 6, 58, 199, 1, 249, 23, 162, 165, 30, 106, 244, 33, 171, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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