Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0a70fe849c9d3ece6bd77b7d2d3ffd2d6eda0e6d4af2b01c338032b0a970e7f

Tx prefix hash: d2f3cfa0c9483f69bd837827217a65a002bb7b2ffd01b0caaba770257d4c9cd5
Tx public key: a335e9cb7fe2c574cfc7e94821348a730e52b5aec81d9b391a34514f4f9a3be5
Timestamp: 1750081497 Timestamp [UCT]: 2025-06-16 13:44:57 Age [y:d:h:m:s]: 00:192:12:13:30
Block: 1306275 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135426 RingCT/type: yes/0
Extra: 01a335e9cb7fe2c574cfc7e94821348a730e52b5aec81d9b391a34514f4f9a3be502110000000301491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a04888ae6436f0b46a876d159fd0c210fd5a0dcc6884c6e588ed52fdca0f93f1 0.600000000000 1793880 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": 1306285, "vin": [ { "gen": { "height": 1306275 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a04888ae6436f0b46a876d159fd0c210fd5a0dcc6884c6e588ed52fdca0f93f1" } } ], "extra": [ 1, 163, 53, 233, 203, 127, 226, 197, 116, 207, 199, 233, 72, 33, 52, 138, 115, 14, 82, 181, 174, 200, 29, 155, 57, 26, 52, 81, 79, 79, 154, 59, 229, 2, 17, 0, 0, 0, 3, 1, 73, 31, 136, 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