Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9681712b5060c1b5dadc5535fe194828fea39311dee2f90ffa2aa68f59df771

Tx prefix hash: 93224002e098ee75a0bdf3e17bd04931f85a66178d155789b6b2303df7347ee5
Tx public key: 0fa017730b25a779b35a309bd1d08cb89cdeb2d173cc298c6f3ce83d8e4a9ed8
Timestamp: 1712362989 Timestamp [UCT]: 2024-04-06 00:23:09 Age [y:d:h:m:s]: 00:168:15:14:08
Block: 994204 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120833 RingCT/type: yes/0
Extra: 010fa017730b25a779b35a309bd1d08cb89cdeb2d173cc298c6f3ce83d8e4a9ed802110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7aaf167da3fb0ea1dd08f5f6649106e1e7644049f8c4dc34d3ad35539b23990 0.600000000000 1454606 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": 994214, "vin": [ { "gen": { "height": 994204 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7aaf167da3fb0ea1dd08f5f6649106e1e7644049f8c4dc34d3ad35539b23990" } } ], "extra": [ 1, 15, 160, 23, 115, 11, 37, 167, 121, 179, 90, 48, 155, 209, 208, 140, 184, 156, 222, 178, 209, 115, 204, 41, 140, 111, 60, 232, 61, 142, 74, 158, 216, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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