Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0569a76bb0f7c386021acfb828e8a46381eabb00558969deb4542ba6128e0183

Tx prefix hash: 65278cad556e3fb439ac1179cda98e9ba87dcf96aca7d51b255f0fae7e042504
Tx public key: fe11163141ef6786046c0d3bdd4c86b3c7cb0cf3e9bd7a18024d0b6f94c84d9b
Timestamp: 1725174631 Timestamp [UCT]: 2024-09-01 07:10:31 Age [y:d:h:m:s]: 00:175:02:22:36
Block: 1100458 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124949 RingCT/type: yes/0
Extra: 01fe11163141ef6786046c0d3bdd4c86b3c7cb0cf3e9bd7a18024d0b6f94c84d9b021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f09f7a5fdf9307b250f248707d6fe4a91182700d593ed823a61e7bcf7d8f9c03 0.600000000000 1576437 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": 1100468, "vin": [ { "gen": { "height": 1100458 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f09f7a5fdf9307b250f248707d6fe4a91182700d593ed823a61e7bcf7d8f9c03" } } ], "extra": [ 1, 254, 17, 22, 49, 65, 239, 103, 134, 4, 108, 13, 59, 221, 76, 134, 179, 199, 203, 12, 243, 233, 189, 122, 24, 2, 77, 11, 111, 148, 200, 77, 155, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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