Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59513b8f992e2f6fed4d3dad28f8725edabad26f5c00c6cb483fbbb728fd045c

Tx prefix hash: 8c149e06be9d782651f6528b80adfce8abf175d847a03f082594042b97b86e55
Tx public key: 35f026269941fd757d9f0a19d92621da511c90975c65af23a7920b8ef1285aa6
Timestamp: 1762460158 Timestamp [UCT]: 2025-11-06 20:15:58 Age [y:d:h:m:s]: 00:085:07:24:53
Block: 1406440 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 60903 RingCT/type: yes/0
Extra: 0135f026269941fd757d9f0a19d92621da511c90975c65af23a7920b8ef1285aa6021100000002a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f2cc66013e05982dd68d6d6f5978172d5ed887a9006a255ee2580f86ab417cd 0.600000000000 1894823 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": 1406450, "vin": [ { "gen": { "height": 1406440 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f2cc66013e05982dd68d6d6f5978172d5ed887a9006a255ee2580f86ab417cd" } } ], "extra": [ 1, 53, 240, 38, 38, 153, 65, 253, 117, 125, 159, 10, 25, 217, 38, 33, 218, 81, 28, 144, 151, 92, 101, 175, 35, 167, 146, 11, 142, 241, 40, 90, 166, 2, 17, 0, 0, 0, 2, 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