Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba1d026c3622dc909ee120c837573f480971570605af0f3950d37c50f239b126

Tx prefix hash: d9076ab262fe826f2e4c0b46a6335edbca63ad06a8b4b20c1ac6aeea96f0a500
Tx public key: 96b96db3ff4f7c8534f1a461b98f17111a5fa3d16f4c97dbac09e42d7544e17d
Timestamp: 1694788303 Timestamp [UCT]: 2023-09-15 14:31:43 Age [y:d:h:m:s]: 01:236:00:11:25
Block: 848727 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 429785 RingCT/type: yes/0
Extra: 0196b96db3ff4f7c8534f1a461b98f17111a5fa3d16f4c97dbac09e42d7544e17d021100000003faf35c9c000000000000000000

1 output(s) for total of 0.945834572000 dcy

stealth address amount amount idx
00: 1ed1b18eaf029c853dfd424ec3a6a33a8272304a2a07d75bb5e5f327e0a0b7df 0.945834572000 1302351 of 0

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": 848737, "vin": [ { "gen": { "height": 848727 } } ], "vout": [ { "amount": 945834572, "target": { "key": "1ed1b18eaf029c853dfd424ec3a6a33a8272304a2a07d75bb5e5f327e0a0b7df" } } ], "extra": [ 1, 150, 185, 109, 179, 255, 79, 124, 133, 52, 241, 164, 97, 185, 143, 23, 17, 26, 95, 163, 209, 111, 76, 151, 219, 172, 9, 228, 45, 117, 68, 225, 125, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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