Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e64a56fa19f6603301c4f1e62745e4ae90f9bfd3d5d15352c03b1abdb2b88959

Tx prefix hash: 2743e6fbd185d8754a39460d82adf2bea4a6fe33b1bdaf4b99bbe7e7393b410f
Tx public key: 79be74e675bbb4e813068b6a85e585bf5da7fbb4cfb54f2a7187fcc444df159d
Timestamp: 1753531487 Timestamp [UCT]: 2025-07-26 12:04:47 Age [y:d:h:m:s]: 00:163:08:13:04
Block: 1333780 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115646 RingCT/type: yes/0
Extra: 0179be74e675bbb4e813068b6a85e585bf5da7fbb4cfb54f2a7187fcc444df159d021100000002db6acbd3000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c95e657c552a56364607ba6b14ff49d79e9ca022753cfee606f712ec0e7cc706 0.600000000000 1821579 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": 1333790, "vin": [ { "gen": { "height": 1333780 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c95e657c552a56364607ba6b14ff49d79e9ca022753cfee606f712ec0e7cc706" } } ], "extra": [ 1, 121, 190, 116, 230, 117, 187, 180, 232, 19, 6, 139, 106, 133, 229, 133, 191, 93, 167, 251, 180, 207, 181, 79, 42, 113, 135, 252, 196, 68, 223, 21, 157, 2, 17, 0, 0, 0, 2, 219, 106, 203, 211, 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