Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80540f3b17ddcfb3952727d8e41aab7d13b125f445715cd4fb1534bae9cfd871

Tx prefix hash: 2753ddeee2700e73403c2cf16e42d3db4be8c483685a85485493dd6f37d520be
Tx public key: 5c92334f5f94bece6be3fa9b6b4001a2cfcb0b2fcc877174adc5c412336e527f
Timestamp: 1708796471 Timestamp [UCT]: 2024-02-24 17:41:11 Age [y:d:h:m:s]: 00:331:07:45:54
Block: 964685 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237123 RingCT/type: yes/0
Extra: 015c92334f5f94bece6be3fa9b6b4001a2cfcb0b2fcc877174adc5c412336e527f0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 528faf84a802fb873a5839409f28f307039cd4c8e6a9d85fc017d5fb8f0a0408 0.600000000000 1424428 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": 964695, "vin": [ { "gen": { "height": 964685 } } ], "vout": [ { "amount": 600000000, "target": { "key": "528faf84a802fb873a5839409f28f307039cd4c8e6a9d85fc017d5fb8f0a0408" } } ], "extra": [ 1, 92, 146, 51, 79, 95, 148, 190, 206, 107, 227, 250, 155, 107, 64, 1, 162, 207, 203, 11, 47, 204, 135, 113, 116, 173, 197, 196, 18, 51, 110, 82, 127, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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