Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08ef2dc720ca82a3aaf7c744e6f272ec6c94f7abb68f142d6bbf0957f8173d5e

Tx prefix hash: 30f6d962424b7f3d008d8d8c7cf2d6c59695fdff7bd785aea8c93e7f1d89660b
Tx public key: 8126a178915a96e1f5254825064b4acb1ed92a2b9b100bf29915e88c7e6e0c34
Timestamp: 1696772464 Timestamp [UCT]: 2023-10-08 13:41:04 Age [y:d:h:m:s]: 01:096:03:58:41
Block: 865199 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329977 RingCT/type: yes/0
Extra: 018126a178915a96e1f5254825064b4acb1ed92a2b9b100bf29915e88c7e6e0c34021100000001faf35c9c000000000000000000

1 output(s) for total of 0.834135464000 dcy

stealth address amount amount idx
00: a623ccee4cf367d8d2dfac13ed7f71322304c32b6901a8442cb70be3bf57bd10 0.834135464000 1319725 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": 865209, "vin": [ { "gen": { "height": 865199 } } ], "vout": [ { "amount": 834135464, "target": { "key": "a623ccee4cf367d8d2dfac13ed7f71322304c32b6901a8442cb70be3bf57bd10" } } ], "extra": [ 1, 129, 38, 161, 120, 145, 90, 150, 225, 245, 37, 72, 37, 6, 75, 74, 203, 30, 217, 42, 43, 155, 16, 11, 242, 153, 21, 232, 140, 126, 110, 12, 52, 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