Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8248632a10857cfae5c4c451ff66f0c23adf191d992960ddc27704c5770d7b27

Tx prefix hash: 792008a2f76f23ea1a7fae167ecadf9faa0d7a39e783fdb2b34261257aba72c4
Tx public key: 8b7a274699cfb7f4347d5827c6843db0bb546f78ecb15a2a08c4299797c9d53b
Timestamp: 1750451302 Timestamp [UCT]: 2025-06-20 20:28:22 Age [y:d:h:m:s]: 00:151:06:27:41
Block: 1309274 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105963 RingCT/type: yes/0
Extra: 018b7a274699cfb7f4347d5827c6843db0bb546f78ecb15a2a08c4299797c9d53b021100000004bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bbfd2aaf10378f9641d4e26ad7b44260e0e199e6ed94cb97a03ec8365dab26e2 0.600000000000 1796889 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": 1309284, "vin": [ { "gen": { "height": 1309274 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bbfd2aaf10378f9641d4e26ad7b44260e0e199e6ed94cb97a03ec8365dab26e2" } } ], "extra": [ 1, 139, 122, 39, 70, 153, 207, 183, 244, 52, 125, 88, 39, 198, 132, 61, 176, 187, 84, 111, 120, 236, 177, 90, 42, 8, 196, 41, 151, 151, 201, 213, 59, 2, 17, 0, 0, 0, 4, 191, 81, 178, 162, 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