Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 995599d8b45ad6ba61802d6d3d646c8a2fe2204a5568b2157c07ba61b89049ea

Tx prefix hash: b42dd25b8175b788827aaa93518a51e68c103e72674b269a29c1d90a57c35687
Tx public key: 646b557f7d3531860a6ad48d9c4627e1aab0a7d88ed81d3ffa214625ebaef2a5
Timestamp: 1714456491 Timestamp [UCT]: 2024-04-30 05:54:51 Age [y:d:h:m:s]: 00:363:21:56:50
Block: 1011591 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 260168 RingCT/type: yes/0
Extra: 01646b557f7d3531860a6ad48d9c4627e1aab0a7d88ed81d3ffa214625ebaef2a50211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: efe9031884874a8ccc33618528c0db4f3ee63e3a9aa3d1fb20a81488bd75a041 0.600000000000 1473863 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": 1011601, "vin": [ { "gen": { "height": 1011591 } } ], "vout": [ { "amount": 600000000, "target": { "key": "efe9031884874a8ccc33618528c0db4f3ee63e3a9aa3d1fb20a81488bd75a041" } } ], "extra": [ 1, 100, 107, 85, 127, 125, 53, 49, 134, 10, 106, 212, 141, 156, 70, 39, 225, 170, 176, 167, 216, 142, 216, 29, 63, 250, 33, 70, 37, 235, 174, 242, 165, 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