Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c5fb6345b7f000febc49fa3c887e1f676db9c9e9eff2b62f7145234a7152050

Tx prefix hash: c05f999e6fcc3001ceeedc15c049f2921d53bcddde42174b55b586f4c2bee6a4
Tx public key: 85ffe844d5329ca5c2e79dc2451d346e2ef979dc5fa0809815fd91441ecc2dd6
Timestamp: 1717088506 Timestamp [UCT]: 2024-05-30 17:01:46 Age [y:d:h:m:s]: 00:237:11:59:07
Block: 1033416 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169927 RingCT/type: yes/0
Extra: 0185ffe844d5329ca5c2e79dc2451d346e2ef979dc5fa0809815fd91441ecc2dd60211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d36e82dec0d4dc76d0f50463656da421c97474f1d6bae3a5eb6c195bb4858f1 0.600000000000 1501883 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": 1033426, "vin": [ { "gen": { "height": 1033416 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d36e82dec0d4dc76d0f50463656da421c97474f1d6bae3a5eb6c195bb4858f1" } } ], "extra": [ 1, 133, 255, 232, 68, 213, 50, 156, 165, 194, 231, 157, 194, 69, 29, 52, 110, 46, 249, 121, 220, 95, 160, 128, 152, 21, 253, 145, 68, 30, 204, 45, 214, 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