Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51a2e782e9f8969e436611aff4eb76df754a2f8f921869901108acc35cfe9bdf

Tx prefix hash: 4d00efbef5a6aeaa2a7a231490cfb3094733df226756bc7a00b48ec27bb915dc
Tx public key: f9e9c4e13e422c707bee6169c466919e86026bbf04b4aaf743d595b07debb3cb
Timestamp: 1713907327 Timestamp [UCT]: 2024-04-23 21:22:07 Age [y:d:h:m:s]: 00:281:08:13:10
Block: 1007047 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201092 RingCT/type: yes/0
Extra: 01f9e9c4e13e422c707bee6169c466919e86026bbf04b4aaf743d595b07debb3cb0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 875d983dc9d3c1acc23e6b78ab5cf6bb08f2969b0798a1f8e27133efa84d7176 0.600000000000 1468265 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": 1007057, "vin": [ { "gen": { "height": 1007047 } } ], "vout": [ { "amount": 600000000, "target": { "key": "875d983dc9d3c1acc23e6b78ab5cf6bb08f2969b0798a1f8e27133efa84d7176" } } ], "extra": [ 1, 249, 233, 196, 225, 62, 66, 44, 112, 123, 238, 97, 105, 196, 102, 145, 158, 134, 2, 107, 191, 4, 180, 170, 247, 67, 213, 149, 176, 125, 235, 179, 203, 2, 17, 0, 0, 0, 1, 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