Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 240674b6912102b6c0598b0dd07cfa4ce1012618eb5cd0e55c884eb30138738f

Tx prefix hash: 2afefa5be3904c0d340e0c47ea21269b991ae6dfa78ddf58c607cbb3eb8aa880
Tx public key: 3cc9db0f9b6210cd34d68dc74c0be85240da14d24fc38cd7ddc6dbcd78af9dc4
Timestamp: 1721770959 Timestamp [UCT]: 2024-07-23 21:42:39 Age [y:d:h:m:s]: 00:259:01:53:50
Block: 1072231 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185077 RingCT/type: yes/0
Extra: 013cc9db0f9b6210cd34d68dc74c0be85240da14d24fc38cd7ddc6dbcd78af9dc4021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac6831a0ddc45a8fba1fa39f3dd4a37c88dcbefedecf30883dea7aed8f81841f 0.600000000000 1544688 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": 1072241, "vin": [ { "gen": { "height": 1072231 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac6831a0ddc45a8fba1fa39f3dd4a37c88dcbefedecf30883dea7aed8f81841f" } } ], "extra": [ 1, 60, 201, 219, 15, 155, 98, 16, 205, 52, 214, 141, 199, 76, 11, 232, 82, 64, 218, 20, 210, 79, 195, 140, 215, 221, 198, 219, 205, 120, 175, 157, 196, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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