Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a37bab44b32d01a651bfdb712e9baad6fff401259eecdcd46d71ac700edf2b6

Tx prefix hash: f592a0f92310f63cb49f09c62911d350644065a903981ed0cb9c0b1a6902a2a4
Tx public key: 9c88aa21aa8150dd13a3d85bb050895d8d9fe9dfe86cee8ee265a5244188ebbe
Timestamp: 1766173254 Timestamp [UCT]: 2025-12-19 19:40:54 Age [y:d:h:m:s]: 00:007:21:59:16
Block: 1437226 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5659 RingCT/type: yes/0
Extra: 019c88aa21aa8150dd13a3d85bb050895d8d9fe9dfe86cee8ee265a5244188ebbe02110000001b7b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d9c7b1ffa4d59c803ab1d654eeac6d6bb682df9e1ebc88106ddea22cc9b53f61 0.600000000000 1926033 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": 1437236, "vin": [ { "gen": { "height": 1437226 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d9c7b1ffa4d59c803ab1d654eeac6d6bb682df9e1ebc88106ddea22cc9b53f61" } } ], "extra": [ 1, 156, 136, 170, 33, 170, 129, 80, 221, 19, 163, 216, 91, 176, 80, 137, 93, 141, 159, 233, 223, 232, 108, 238, 142, 226, 101, 165, 36, 65, 136, 235, 190, 2, 17, 0, 0, 0, 27, 123, 30, 81, 172, 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