Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a3600dfae1f9c58b79c519697dd9646de1a783972c39b6e939704b6531e0ec3

Tx prefix hash: 4b5149f7a34a885b2c4ed56c50330843af89d53715b3e0d90e97278ecce1b027
Tx public key: ae8426983cb42ae3a737ddb8cda7af09e0227b2f043be4e2652a5b3934c35096
Timestamp: 1755539540 Timestamp [UCT]: 2025-08-18 17:52:20 Age [y:d:h:m:s]: 00:094:10:09:47
Block: 1349334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67356 RingCT/type: yes/0
Extra: 01ae8426983cb42ae3a737ddb8cda7af09e0227b2f043be4e2652a5b3934c35096021100000003a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e4c75466739f7b4d9bc3dbabd1fd8717d349701690ae58d3544d60067dae533a 0.600000000000 1837265 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": 1349344, "vin": [ { "gen": { "height": 1349334 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4c75466739f7b4d9bc3dbabd1fd8717d349701690ae58d3544d60067dae533a" } } ], "extra": [ 1, 174, 132, 38, 152, 60, 180, 42, 227, 167, 55, 221, 184, 205, 167, 175, 9, 224, 34, 123, 47, 4, 59, 228, 226, 101, 42, 91, 57, 52, 195, 80, 150, 2, 17, 0, 0, 0, 3, 161, 29, 186, 152, 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