Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a10560c655007ff1cbca4445f39e3c9a9c36ea3b6d629ed9831b5ee77cf5e3a7

Tx prefix hash: 44c2cd24eba463df265a8654bd9b0070dc3827ec93168944d7e72edba84188b5
Tx public key: d9b93b70236cffbc232f83b85e7a6a6692ba27b6bdaac7459e5016f1c7b285aa
Timestamp: 1747885723 Timestamp [UCT]: 2025-05-22 03:48:43 Age [y:d:h:m:s]: 00:130:15:02:25
Block: 1288217 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90965 RingCT/type: yes/0
Extra: 01d9b93b70236cffbc232f83b85e7a6a6692ba27b6bdaac7459e5016f1c7b285aa0211000000079f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f4e796b33168430b253f73f85e0b366ef7956bd49d6f35734e369aa115d16f9 0.600000000000 1775684 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": 1288227, "vin": [ { "gen": { "height": 1288217 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f4e796b33168430b253f73f85e0b366ef7956bd49d6f35734e369aa115d16f9" } } ], "extra": [ 1, 217, 185, 59, 112, 35, 108, 255, 188, 35, 47, 131, 184, 94, 122, 106, 102, 146, 186, 39, 182, 189, 170, 199, 69, 158, 80, 22, 241, 199, 178, 133, 170, 2, 17, 0, 0, 0, 7, 159, 159, 230, 140, 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