Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95bd4ee062ed333b977e1d8d13bc7dd644dd85c670e7d9e029fa0022652ee420

Tx prefix hash: 4c08101f6d8c144b00ea0273317692f2029641f6fbf4cdac2f3c89833a6a0114
Tx public key: df6e4d09fcb5f8778861ba1e15a701037953ce219ce251c5fe0653a81bd3ff26
Timestamp: 1696934199 Timestamp [UCT]: 2023-10-10 10:36:39 Age [y:d:h:m:s]: 01:105:18:18:00
Block: 866537 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336805 RingCT/type: yes/0
Extra: 01df6e4d09fcb5f8778861ba1e15a701037953ce219ce251c5fe0653a81bd3ff26021100000010e6d27f9c000000000000000000

1 output(s) for total of 0.825663782000 dcy

stealth address amount amount idx
00: d9e7fd7926efafbc48a59fa0c325ec242e099f676ad644575ff6fe776e778d0f 0.825663782000 1321141 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": 866547, "vin": [ { "gen": { "height": 866537 } } ], "vout": [ { "amount": 825663782, "target": { "key": "d9e7fd7926efafbc48a59fa0c325ec242e099f676ad644575ff6fe776e778d0f" } } ], "extra": [ 1, 223, 110, 77, 9, 252, 181, 248, 119, 136, 97, 186, 30, 21, 167, 1, 3, 121, 83, 206, 33, 156, 226, 81, 197, 254, 6, 83, 168, 27, 211, 255, 38, 2, 17, 0, 0, 0, 16, 230, 210, 127, 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