Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 471a1485559d8dfd1856068c920ccffe7204e6087bb5c780e19ea6cb8217b219

Tx prefix hash: bfb01eebc250e7768ea9786e96f479bd91ae74f0681064c24a8efe326f69460b
Tx public key: 4442e2905c467c3a9a350969b76f39e1b4b894f9455b3d28e3c21e1b46bdd090
Timestamp: 1754790994 Timestamp [UCT]: 2025-08-10 01:56:34 Age [y:d:h:m:s]: 00:098:00:31:36
Block: 1343848 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69231 RingCT/type: yes/0
Extra: 014442e2905c467c3a9a350969b76f39e1b4b894f9455b3d28e3c21e1b46bdd0900211000000028368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 310ffac44e05c23a5ed76fc0f0cce816659491d13dce9b19c4c5abbb69e0716d 0.600000000000 1831691 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": 1343858, "vin": [ { "gen": { "height": 1343848 } } ], "vout": [ { "amount": 600000000, "target": { "key": "310ffac44e05c23a5ed76fc0f0cce816659491d13dce9b19c4c5abbb69e0716d" } } ], "extra": [ 1, 68, 66, 226, 144, 92, 70, 124, 58, 154, 53, 9, 105, 183, 111, 57, 225, 180, 184, 148, 249, 69, 91, 61, 40, 227, 194, 30, 27, 70, 189, 208, 144, 2, 17, 0, 0, 0, 2, 131, 104, 38, 109, 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