Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 580ec624117ef888a49fe0c4f36721cb86456733123f03ba7df1363b2674dbc4

Tx prefix hash: f0cdc74fd5277058c6661ad4c9464c49c8e8d6d344b04a0da8041ff9b04ccddc
Tx public key: 8a60dde0d7907301e03f78323b47db6b99f7851a4423b8ca479096b5d3b2c53c
Timestamp: 1759767440 Timestamp [UCT]: 2025-10-06 16:17:20 Age [y:d:h:m:s]: 00:036:16:54:54
Block: 1384128 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 26282 RingCT/type: yes/0
Extra: 018a60dde0d7907301e03f78323b47db6b99f7851a4423b8ca479096b5d3b2c53c021100000007a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 10cdf3940d72d0debab6fbbb4fda9d32a7e991e67fd9a27473953784d7b2423d 0.600000000000 1872277 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": 1384138, "vin": [ { "gen": { "height": 1384128 } } ], "vout": [ { "amount": 600000000, "target": { "key": "10cdf3940d72d0debab6fbbb4fda9d32a7e991e67fd9a27473953784d7b2423d" } } ], "extra": [ 1, 138, 96, 221, 224, 215, 144, 115, 1, 224, 63, 120, 50, 59, 71, 219, 107, 153, 247, 133, 26, 68, 35, 184, 202, 71, 144, 150, 181, 211, 178, 197, 60, 2, 17, 0, 0, 0, 7, 165, 220, 205, 121, 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