Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 975f0ca53419fd44a8eda0862943f4e53360b7551d647f4cee66fe24837965cd

Tx prefix hash: 940f6c72bcd99fb53f6c94c10d50ef2d0820ae94c45955a603e0636e98f0d3fb
Tx public key: 85039ade4d0bec8cd6f8cbda0e8903a9f6915a22448b242ff8630a98d7c8064e
Timestamp: 1751859675 Timestamp [UCT]: 2025-07-07 03:41:15 Age [y:d:h:m:s]: 00:134:05:35:47
Block: 1320357 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94357 RingCT/type: yes/0
Extra: 0185039ade4d0bec8cd6f8cbda0e8903a9f6915a22448b242ff8630a98d7c8064e021100000005bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f93c739a7182bae65e9ed6f25f54d60c75c2e8ad30300d9f9399eb9476ad25ea 0.600000000000 1808054 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": 1320367, "vin": [ { "gen": { "height": 1320357 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f93c739a7182bae65e9ed6f25f54d60c75c2e8ad30300d9f9399eb9476ad25ea" } } ], "extra": [ 1, 133, 3, 154, 222, 77, 11, 236, 140, 214, 248, 203, 218, 14, 137, 3, 169, 246, 145, 90, 34, 68, 139, 36, 47, 248, 99, 10, 152, 215, 200, 6, 78, 2, 17, 0, 0, 0, 5, 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