Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 999b26860160841b81636e0fe449869e5da1dccea67ec8a80f997aae68a96d23

Tx prefix hash: a1851426eb7c9d988813c82559d2eb65a76ea4861b24612e0cc3f53253d5e2d5
Tx public key: 2ed8f7d30c9991d9fdaf5e76e1957777bf076dc70d69871611f35024b8dc6dc9
Timestamp: 1709016461 Timestamp [UCT]: 2024-02-27 06:47:41 Age [y:d:h:m:s]: 01:252:16:25:58
Block: 966506 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 439296 RingCT/type: yes/0
Extra: 012ed8f7d30c9991d9fdaf5e76e1957777bf076dc70d69871611f35024b8dc6dc90211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25df5763764849816db3f7c5ddc165c7c076273cdad7373895ca6a29215dd858 0.600000000000 1426265 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": 966516, "vin": [ { "gen": { "height": 966506 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25df5763764849816db3f7c5ddc165c7c076273cdad7373895ca6a29215dd858" } } ], "extra": [ 1, 46, 216, 247, 211, 12, 153, 145, 217, 253, 175, 94, 118, 225, 149, 119, 119, 191, 7, 109, 199, 13, 105, 135, 22, 17, 243, 80, 36, 184, 220, 109, 201, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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