Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae7ff96c20e2ce1fcd0aef15d9a86c65971885d784a30ae2d574b47138f03190

Tx prefix hash: 92ff919a82e6525f0405a762b3cd0fbcca1fe3b6072050e58dfc6fe62c7503e6
Tx public key: 28e0a252257781e9f2310de5db178df0f68908a982b8823270e49da4a5c4bd4e
Timestamp: 1763724474 Timestamp [UCT]: 2025-11-21 11:27:54 Age [y:d:h:m:s]: 00:043:17:32:39
Block: 1416915 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 31330 RingCT/type: yes/0
Extra: 0128e0a252257781e9f2310de5db178df0f68908a982b8823270e49da4a5c4bd4e021100000002d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e3e7cad9761c140a8cca5c5705cf1baddcf9dcf135f70a070b18dc3decfdaf0 0.600000000000 1905436 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": 1416925, "vin": [ { "gen": { "height": 1416915 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e3e7cad9761c140a8cca5c5705cf1baddcf9dcf135f70a070b18dc3decfdaf0" } } ], "extra": [ 1, 40, 224, 162, 82, 37, 119, 129, 233, 242, 49, 13, 229, 219, 23, 141, 240, 246, 137, 8, 169, 130, 184, 130, 50, 112, 228, 157, 164, 165, 196, 189, 78, 2, 17, 0, 0, 0, 2, 214, 225, 157, 124, 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