Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6595c6e11351506a29081ca0d92b5cb020c19de95065a7fd58f303e360f70fbb

Tx prefix hash: d3c49213d0493bb517aadfb4162f3f4271d78e6f24040a0654088b76fa6a1fd9
Tx public key: a77aab0afa6009b72fb706c6bba93d6bd014f8101d59e12c7eab94dda6231e9f
Timestamp: 1763424540 Timestamp [UCT]: 2025-11-18 00:09:00 Age [y:d:h:m:s]: 00:046:12:42:44
Block: 1414441 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 33317 RingCT/type: yes/0
Extra: 01a77aab0afa6009b72fb706c6bba93d6bd014f8101d59e12c7eab94dda6231e9f021100000003d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b7f9ed5c982767d4a822367fe3a51216649216006ac625e24c34d3607c477b1 0.600000000000 1902930 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": 1414451, "vin": [ { "gen": { "height": 1414441 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b7f9ed5c982767d4a822367fe3a51216649216006ac625e24c34d3607c477b1" } } ], "extra": [ 1, 167, 122, 171, 10, 250, 96, 9, 183, 47, 183, 6, 198, 187, 169, 61, 107, 208, 20, 248, 16, 29, 89, 225, 44, 126, 171, 148, 221, 166, 35, 30, 159, 2, 17, 0, 0, 0, 3, 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