Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00193731b1005152bdb72c9f6e18f3a4e927eed3f2d45c3e760ce75bc5ec6e8c

Tx prefix hash: 467dc5d8ae5997676cd90dfb4fe74db2836a411a0f9ee555820d225a03f92e08
Tx public key: 07b9518654c826dd22ede325fdf4427803c245abc44dcca4d9b52509c8fcc054
Timestamp: 1765459039 Timestamp [UCT]: 2025-12-11 13:17:19 Age [y:d:h:m:s]: 00:010:23:00:23
Block: 1431303 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7836 RingCT/type: yes/0
Extra: 0107b9518654c826dd22ede325fdf4427803c245abc44dcca4d9b52509c8fcc054021100000010d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31c363296e2a6798ba428aab56c6de08b2b3ed731b09c967d67d9d132c253072 0.600000000000 1920060 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": 1431313, "vin": [ { "gen": { "height": 1431303 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31c363296e2a6798ba428aab56c6de08b2b3ed731b09c967d67d9d132c253072" } } ], "extra": [ 1, 7, 185, 81, 134, 84, 200, 38, 221, 34, 237, 227, 37, 253, 244, 66, 120, 3, 194, 69, 171, 196, 77, 204, 164, 217, 181, 37, 9, 200, 252, 192, 84, 2, 17, 0, 0, 0, 16, 214, 225, 157, 124, 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