Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6a1dea0ac5f1e5af3c7b4114790014d94029dfb4498d054c0b03645a6b68e7e

Tx prefix hash: 7d92e175db1fbf2ca52c1aa7415ef7e88d29d26e5cb78c91ac4f6e45059649e8
Tx public key: a7aa4d40cd86bb18078bfe73484beea10bae8fe29cbac6f002e9326692debbef
Timestamp: 1724448310 Timestamp [UCT]: 2024-08-23 21:25:10 Age [y:d:h:m:s]: 00:092:10:21:17
Block: 1094454 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66094 RingCT/type: yes/0
Extra: 01a7aa4d40cd86bb18078bfe73484beea10bae8fe29cbac6f002e9326692debbef02110000001091e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7da40d836770d66b0c01e020310ed0399d847f39eed6e536bf83239f1ef9f6cb 0.600000000000 1569571 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": 1094464, "vin": [ { "gen": { "height": 1094454 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7da40d836770d66b0c01e020310ed0399d847f39eed6e536bf83239f1ef9f6cb" } } ], "extra": [ 1, 167, 170, 77, 64, 205, 134, 187, 24, 7, 139, 254, 115, 72, 75, 238, 161, 11, 174, 143, 226, 156, 186, 198, 240, 2, 233, 50, 102, 146, 222, 187, 239, 2, 17, 0, 0, 0, 16, 145, 225, 60, 4, 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