Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6aeab999d71de0f51ff61fea3a7116808b7c7a29f7d43b6972d750cd29234f2

Tx prefix hash: cf4da61e58518fcea3462839cac5c4ac75dae6810a5d8e36e55c1a5d25e93e37
Tx public key: bbbb254156ae5d0ff58f54677a645950653ab77a390f0ab359f28e3efdc833b9
Timestamp: 1763488291 Timestamp [UCT]: 2025-11-18 17:51:31 Age [y:d:h:m:s]: 00:009:12:03:52
Block: 1414973 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6799 RingCT/type: yes/0
Extra: 01bbbb254156ae5d0ff58f54677a645950653ab77a390f0ab359f28e3efdc833b902110000000170609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2b7e7b226f6fc25aac7fc35713e9d4e9d388b64db2dc20c17f8cf7d07a10488 0.600000000000 1903466 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": 1414983, "vin": [ { "gen": { "height": 1414973 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2b7e7b226f6fc25aac7fc35713e9d4e9d388b64db2dc20c17f8cf7d07a10488" } } ], "extra": [ 1, 187, 187, 37, 65, 86, 174, 93, 15, 245, 143, 84, 103, 122, 100, 89, 80, 101, 58, 183, 122, 57, 15, 10, 179, 89, 242, 142, 62, 253, 200, 51, 185, 2, 17, 0, 0, 0, 1, 112, 96, 157, 3, 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