Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42939f44c4af4d5f6ce11eddf9a56d8ddfbb5454cd4c499aeb774e4de6bef2a3

Tx prefix hash: 2bacb0079d4b29fb2342a60164598a47e74f59e3eb12b73159c2a70a3330c34e
Tx public key: 36533ca64bf66b6a928f82122b262f158c84e0969ef3e77e2fa8b9069150172d
Timestamp: 1752601741 Timestamp [UCT]: 2025-07-15 17:49:01 Age [y:d:h:m:s]: 00:135:13:03:05
Block: 1326174 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95626 RingCT/type: yes/0
Extra: 0136533ca64bf66b6a928f82122b262f158c84e0969ef3e77e2fa8b9069150172d021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6899ba5ddbdf1f859c42550eecba2706a541c2d88e987f3c0d3456c0eb2e8f1d 0.600000000000 1813923 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": 1326184, "vin": [ { "gen": { "height": 1326174 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6899ba5ddbdf1f859c42550eecba2706a541c2d88e987f3c0d3456c0eb2e8f1d" } } ], "extra": [ 1, 54, 83, 60, 166, 75, 246, 107, 106, 146, 143, 130, 18, 43, 38, 47, 21, 140, 132, 224, 150, 158, 243, 231, 126, 47, 168, 185, 6, 145, 80, 23, 45, 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