Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 025fc957eb45bc5b6c2946eabd66cb61a15846f1033f89236055623c296e2a23

Tx prefix hash: 9e0a4ceec815974365fad37328773eac4d4655c4f431a937e34df5c95947f7b2
Tx public key: 7d3865f18f786c8e59a287922ea7699eba6f0daf2c1f2e3f5c53e50c490071d5
Timestamp: 1719170087 Timestamp [UCT]: 2024-06-23 19:14:47 Age [y:d:h:m:s]: 00:326:05:34:27
Block: 1050662 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233152 RingCT/type: yes/0
Extra: 017d3865f18f786c8e59a287922ea7699eba6f0daf2c1f2e3f5c53e50c490071d50211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ee0dca0b72f2d8021c30b57d01dfefc8c129778325815048c69d8a1c974fef8 0.600000000000 1520837 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": 1050672, "vin": [ { "gen": { "height": 1050662 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ee0dca0b72f2d8021c30b57d01dfefc8c129778325815048c69d8a1c974fef8" } } ], "extra": [ 1, 125, 56, 101, 241, 143, 120, 108, 142, 89, 162, 135, 146, 46, 167, 105, 158, 186, 111, 13, 175, 44, 31, 46, 63, 92, 83, 229, 12, 73, 0, 113, 213, 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