Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f304a3bf9416ea7a129a2bdc35a2247436eaae6857946bb4637a0c10bd92563

Tx prefix hash: 9ceed76edb88ff97a58cf88ed3135bbc34f6fb1fd1ed86d23c6298c3b86e60d4
Tx public key: 8b54cc813fffddd9234471c3b302b46ae8216cac305f10f13ed1fd4f1f41f429
Timestamp: 1755010351 Timestamp [UCT]: 2025-08-12 14:52:31 Age [y:d:h:m:s]: 00:148:14:01:34
Block: 1345529 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105577 RingCT/type: yes/0
Extra: 018b54cc813fffddd9234471c3b302b46ae8216cac305f10f13ed1fd4f1f41f4290211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c66292995be081c2acf0433442044fc768e40d45b18e18d75a4baba532d5197 0.600000000000 1833422 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": 1345539, "vin": [ { "gen": { "height": 1345529 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c66292995be081c2acf0433442044fc768e40d45b18e18d75a4baba532d5197" } } ], "extra": [ 1, 139, 84, 204, 129, 63, 255, 221, 217, 35, 68, 113, 195, 179, 2, 180, 106, 232, 33, 108, 172, 48, 95, 16, 241, 62, 209, 253, 79, 31, 65, 244, 41, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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