Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41be98dac8ae414e086560d323ae5e7edaa4e7078e3ccfe31a1c8f0086838e86

Tx prefix hash: 9f1da077df6c2a18da4c1282206eab22471c36993de34261a1c81ddd0d7238b9
Tx public key: 589e166ca9060c7c4a47fe959cef8790b9f129a9d8ab620438b406631f100130
Timestamp: 1726819348 Timestamp [UCT]: 2024-09-20 08:02:28 Age [y:d:h:m:s]: 00:111:20:01:54
Block: 1114091 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79965 RingCT/type: yes/0
Extra: 01589e166ca9060c7c4a47fe959cef8790b9f129a9d8ab620438b406631f100130021100000001bdafe9cc000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b7ddc06da7ec47e56d09b16a2abdfd75c446f0362292978c535ccb1d3a7fd40 0.600000000000 1593888 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": 1114101, "vin": [ { "gen": { "height": 1114091 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b7ddc06da7ec47e56d09b16a2abdfd75c446f0362292978c535ccb1d3a7fd40" } } ], "extra": [ 1, 88, 158, 22, 108, 169, 6, 12, 124, 74, 71, 254, 149, 156, 239, 135, 144, 185, 241, 41, 169, 216, 171, 98, 4, 56, 180, 6, 99, 31, 16, 1, 48, 2, 17, 0, 0, 0, 1, 189, 175, 233, 204, 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