Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a664c2e19f7e84488db49117d8e3da24782f7c58781cc2c0be25e324dee8b724

Tx prefix hash: 03af2723a316ae4ff197ca4d525d7dc93668ae76c336754dee25aba8cca25d86
Tx public key: ad15b3fa87a171a5ea3a98dcb27ab63cfcd4a76a50ba363e9c1ed3a146d92e26
Timestamp: 1737612554 Timestamp [UCT]: 2025-01-23 06:09:14 Age [y:d:h:m:s]: 00:345:18:27:19
Block: 1203373 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244740 RingCT/type: yes/0
Extra: 01ad15b3fa87a171a5ea3a98dcb27ab63cfcd4a76a50ba363e9c1ed3a146d92e26021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d269a7236f34b15cf06eb0035c4400eb8c11d9645ef9df383ac09a7c84e7438a 0.600000000000 1690050 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": 1203383, "vin": [ { "gen": { "height": 1203373 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d269a7236f34b15cf06eb0035c4400eb8c11d9645ef9df383ac09a7c84e7438a" } } ], "extra": [ 1, 173, 21, 179, 250, 135, 161, 113, 165, 234, 58, 152, 220, 178, 122, 182, 60, 252, 212, 167, 106, 80, 186, 54, 62, 156, 30, 211, 161, 70, 217, 46, 38, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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