Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4e77dec3b4d2bef68ea7c572a4b0dce4354d60468a0514d3ac12ff3d1072571

Tx prefix hash: fa51bc509e82d6d7d608074e99af4f1e674be4e766eead48dd54a986670d34af
Tx public key: 9ad7d551e28cffdef5011a7d5f27d126e0853a8dbc70b5ba09dbe72d21fa1e6d
Timestamp: 1765106109 Timestamp [UCT]: 2025-12-07 11:15:09 Age [y:d:h:m:s]: 00:021:01:41:44
Block: 1428386 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 15080 RingCT/type: yes/0
Extra: 019ad7d551e28cffdef5011a7d5f27d126e0853a8dbc70b5ba09dbe72d21fa1e6d02110000000d70609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3c8a87f2dab2a91633e2eb0287f8b0edd5f07fc2f6c867e96f4215810569f45 0.600000000000 1917103 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": 1428396, "vin": [ { "gen": { "height": 1428386 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3c8a87f2dab2a91633e2eb0287f8b0edd5f07fc2f6c867e96f4215810569f45" } } ], "extra": [ 1, 154, 215, 213, 81, 226, 140, 255, 222, 245, 1, 26, 125, 95, 39, 209, 38, 224, 133, 58, 141, 188, 112, 181, 186, 9, 219, 231, 45, 33, 250, 30, 109, 2, 17, 0, 0, 0, 13, 112, 96, 157, 3, 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