Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 829674c912592a21b2da74a11cb742f4823d7282ae2771bc3cdcb232443fa97e

Tx prefix hash: d8a4f00af52f816f1f9ca424480609dd4351bad56fa02f9e35809a51bb043add
Tx public key: 1b9b6d5fcb63f191952841ecd83927a44b535871c4f84079a6f180b46fab5ecd
Timestamp: 1733160854 Timestamp [UCT]: 2024-12-02 17:34:14 Age [y:d:h:m:s]: 00:025:16:48:07
Block: 1166567 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18384 RingCT/type: yes/0
Extra: 011b9b6d5fcb63f191952841ecd83927a44b535871c4f84079a6f180b46fab5ecd021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a98afbde3d7e8ab2e539ca92a8f9d99de27372a458c9936b2b6631c97cd7828 0.600000000000 1652254 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": 1166577, "vin": [ { "gen": { "height": 1166567 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a98afbde3d7e8ab2e539ca92a8f9d99de27372a458c9936b2b6631c97cd7828" } } ], "extra": [ 1, 27, 155, 109, 95, 203, 99, 241, 145, 149, 40, 65, 236, 216, 57, 39, 164, 75, 83, 88, 113, 196, 248, 64, 121, 166, 241, 128, 180, 111, 171, 94, 205, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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