Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a625895ecff7326213d508c625a4d7951a9e9ea5f49a2466bd3fd1d5ecbf7bd

Tx prefix hash: 16202db218d9be2988f7948c52390e70149e685b02306b85544e87ad7a0583bd
Tx public key: 9f6a2923b869f47b309756b5f243c0048e37b363fcc14d750e7b3d158fbd460e
Timestamp: 1706692268 Timestamp [UCT]: 2024-01-31 09:11:08 Age [y:d:h:m:s]: 01:277:18:00:24
Block: 947207 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 457302 RingCT/type: yes/0
Extra: 019f6a2923b869f47b309756b5f243c0048e37b363fcc14d750e7b3d158fbd460e02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6a370e68b166207b71beb2d826d2d3ca6c029e49574b42389a70faaf111c6883 0.600000000000 1405555 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": 947217, "vin": [ { "gen": { "height": 947207 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a370e68b166207b71beb2d826d2d3ca6c029e49574b42389a70faaf111c6883" } } ], "extra": [ 1, 159, 106, 41, 35, 184, 105, 244, 123, 48, 151, 86, 181, 242, 67, 192, 4, 142, 55, 179, 99, 252, 193, 77, 117, 14, 123, 61, 21, 143, 189, 70, 14, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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