Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eaa948f156a4ba8c98370eefa37780e61dc016cd44a6404f92f56e0d75b6ffea

Tx prefix hash: 7a8ee115a7408f826843b81b28b0209276a454f9dc40805059b8b47ac0a610a6
Tx public key: 1eb8232b935c3ab57035c9c551ae7c42246672c1048852f7b05ba86755ba18b2
Timestamp: 1707481329 Timestamp [UCT]: 2024-02-09 12:22:09 Age [y:d:h:m:s]: 01:056:11:08:03
Block: 953765 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301400 RingCT/type: yes/0
Extra: 011eb8232b935c3ab57035c9c551ae7c42246672c1048852f7b05ba86755ba18b202110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b26d1fe1e4cbe16879b0b4f8ea2da6449b05a8f8d5f6cf9160f1074f2ab2b48 0.600000000000 1413013 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": 953775, "vin": [ { "gen": { "height": 953765 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b26d1fe1e4cbe16879b0b4f8ea2da6449b05a8f8d5f6cf9160f1074f2ab2b48" } } ], "extra": [ 1, 30, 184, 35, 43, 147, 92, 58, 181, 112, 53, 201, 197, 81, 174, 124, 66, 36, 102, 114, 193, 4, 136, 82, 247, 176, 91, 168, 103, 85, 186, 24, 178, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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