Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab1aa1f15e928d8572e8615bfbf0a28d181c127c51c23b91790548ff5506dc37

Tx prefix hash: 8905f2b97d1c40a82c9878dfeb524500bb4b73a7a4114bb9170475f6f5ad2b23
Tx public key: 7200eaef2f3a252901bde49f3d790ebada46f8dc2f66002ae5b17d8445ecc638
Timestamp: 1708919204 Timestamp [UCT]: 2024-02-26 03:46:44 Age [y:d:h:m:s]: 01:080:16:46:26
Block: 965696 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318711 RingCT/type: yes/0
Extra: 017200eaef2f3a252901bde49f3d790ebada46f8dc2f66002ae5b17d8445ecc6380211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 93c77540add3851819552f8df38dd9b6a662f58ffe89994779f3b0c7b68c19ac 0.600000000000 1425451 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": 965706, "vin": [ { "gen": { "height": 965696 } } ], "vout": [ { "amount": 600000000, "target": { "key": "93c77540add3851819552f8df38dd9b6a662f58ffe89994779f3b0c7b68c19ac" } } ], "extra": [ 1, 114, 0, 234, 239, 47, 58, 37, 41, 1, 189, 228, 159, 61, 121, 14, 186, 218, 70, 248, 220, 47, 102, 0, 42, 229, 177, 125, 132, 69, 236, 198, 56, 2, 17, 0, 0, 0, 4, 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