Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea64f939d1c9cc45401234c7ddd9dfde9aba4338a0ea602f590db4a780a390f2

Tx prefix hash: 6097bd2b34013f0bbcd544ac6c7be9c66951abac00573c420eb14de55cc852a7
Tx public key: 7893baa3016201dfa5880b753e2c53dea269def2ec3ef0c783b85db8a80fcb6d
Timestamp: 1700900751 Timestamp [UCT]: 2023-11-25 08:25:51 Age [y:d:h:m:s]: 01:203:18:10:58
Block: 899210 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 406742 RingCT/type: yes/0
Extra: 017893baa3016201dfa5880b753e2c53dea269def2ec3ef0c783b85db8a80fcb6d021100000006e6d27f9c000000000000000000

1 output(s) for total of 0.643493219000 dcy

stealth address amount amount idx
00: f8e0c8a93063f91ac832d5a756c9d744534addb91a74210b990f4a7e74fceffd 0.643493219000 1355655 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": 899220, "vin": [ { "gen": { "height": 899210 } } ], "vout": [ { "amount": 643493219, "target": { "key": "f8e0c8a93063f91ac832d5a756c9d744534addb91a74210b990f4a7e74fceffd" } } ], "extra": [ 1, 120, 147, 186, 163, 1, 98, 1, 223, 165, 136, 11, 117, 62, 44, 83, 222, 162, 105, 222, 242, 236, 62, 240, 199, 131, 184, 93, 184, 168, 15, 203, 109, 2, 17, 0, 0, 0, 6, 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