Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c00b824f03b3329586629b3fcf5d4ff38d2e12c1a4184d6ff4082a2d5c89a635

Tx prefix hash: e8775d19ee35458f2806a3ecb24a03bcbfa759efaafc27b9f563075e1e850967
Tx public key: 23a1cb376e757b1d2eebd04450277e5ed8af128684b2222b0c9fac613ca8ef68
Timestamp: 1714702954 Timestamp [UCT]: 2024-05-03 02:22:34 Age [y:d:h:m:s]: 01:011:21:57:09
Block: 1013651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 269444 RingCT/type: yes/0
Extra: 0123a1cb376e757b1d2eebd04450277e5ed8af128684b2222b0c9fac613ca8ef6802110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45ae3e78749709f98f9792bf23b60c41a5caa93004c0ef65fc7f1c274c41d347 0.600000000000 1476522 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": 1013661, "vin": [ { "gen": { "height": 1013651 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45ae3e78749709f98f9792bf23b60c41a5caa93004c0ef65fc7f1c274c41d347" } } ], "extra": [ 1, 35, 161, 203, 55, 110, 117, 123, 29, 46, 235, 208, 68, 80, 39, 126, 94, 216, 175, 18, 134, 132, 178, 34, 43, 12, 159, 172, 97, 60, 168, 239, 104, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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