Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3e2a23660426e9a036f8b295df64e44d0ac47798980e868168a7f1691efdfff

Tx prefix hash: f9f298b5237f9dcf77f17193b1296cdff1f77cb7a988b1d5f9b804a6d96de832
Tx public key: b069457a55aac974710caa8bb0ce868602cd87179e293b849158af6bf7b6cb57
Timestamp: 1758254907 Timestamp [UCT]: 2025-09-19 04:08:27 Age [y:d:h:m:s]: 00:112:03:45:15
Block: 1371601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80307 RingCT/type: yes/0
Extra: 01b069457a55aac974710caa8bb0ce868602cd87179e293b849158af6bf7b6cb57021100000002ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0320bb8b2c4e21149c40bef575b2507ba8d3faad62621a2a45a5e5f9e40f7cf 0.600000000000 1859678 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": 1371611, "vin": [ { "gen": { "height": 1371601 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0320bb8b2c4e21149c40bef575b2507ba8d3faad62621a2a45a5e5f9e40f7cf" } } ], "extra": [ 1, 176, 105, 69, 122, 85, 170, 201, 116, 113, 12, 170, 139, 176, 206, 134, 134, 2, 205, 135, 23, 158, 41, 59, 132, 145, 88, 175, 107, 247, 182, 203, 87, 2, 17, 0, 0, 0, 2, 173, 121, 72, 208, 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