Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0cb53e4ff93177aebb6e460d19c963cfefb89e24f573ba97a8105b34d46cc14

Tx prefix hash: 0617956cf6123d6f0fc35ee23a9fff25202f631b6569dcda361e83b9a16487e5
Tx public key: 8c103d3e45f384d3a034c880adbbcd3b5656ff169f47add8f7e925b26ea1d319
Timestamp: 1718131370 Timestamp [UCT]: 2024-06-11 18:42:50 Age [y:d:h:m:s]: 01:148:07:00:39
Block: 1042072 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364530 RingCT/type: yes/0
Extra: 018c103d3e45f384d3a034c880adbbcd3b5656ff169f47add8f7e925b26ea1d31902110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ebabf377a280d2ad43f3e663461ebace5f956c4a1685a91846d38565ddb97c37 0.600000000000 1510899 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": 1042082, "vin": [ { "gen": { "height": 1042072 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ebabf377a280d2ad43f3e663461ebace5f956c4a1685a91846d38565ddb97c37" } } ], "extra": [ 1, 140, 16, 61, 62, 69, 243, 132, 211, 160, 52, 200, 128, 173, 187, 205, 59, 86, 86, 255, 22, 159, 71, 173, 216, 247, 233, 37, 178, 110, 161, 211, 25, 2, 17, 0, 0, 0, 2, 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