Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: edc10fc75aca0e89dc5d3db0dac9f43693a18f1328bca7212165cd30387f5135

Tx prefix hash: 701d71713d1267156f1aaa7d1c3fe496fd22bd0fdb0c3401ae734aec4757d01e
Tx public key: 7e5f9da03339c4e1583d0d8eb5ab966a8f8658254867abd2b4e8229e65aaf2ff
Timestamp: 1755413461 Timestamp [UCT]: 2025-08-17 06:51:01 Age [y:d:h:m:s]: 00:049:18:26:17
Block: 1348341 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 35334 RingCT/type: yes/0
Extra: 017e5f9da03339c4e1583d0d8eb5ab966a8f8658254867abd2b4e8229e65aaf2ff021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600080000000 dcy

stealth address amount amount idx
00: 6442822edaeb4fa2190e36500b14abeecab7f3a4f489fd3a2c49fdd7d3670286 0.600080000000 1836266 of 0

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": 1348351, "vin": [ { "gen": { "height": 1348341 } } ], "vout": [ { "amount": 600080000, "target": { "key": "6442822edaeb4fa2190e36500b14abeecab7f3a4f489fd3a2c49fdd7d3670286" } } ], "extra": [ 1, 126, 95, 157, 160, 51, 57, 196, 225, 88, 61, 13, 142, 181, 171, 150, 106, 143, 134, 88, 37, 72, 103, 171, 210, 180, 232, 34, 158, 101, 170, 242, 255, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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