Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c51385ca7a9cef7b2337128b01ffd824c53ddb913c170dc7b146b5ffbf220d16

Tx prefix hash: 35c9163581b0b66777eacf8feec2fa619f777dbefa7544354155a2ef3af2b1cf
Tx public key: 4422e915c6878185d707db09ce3ea5c553d87f7cb689134c2a4fa54b68652206
Timestamp: 1699484679 Timestamp [UCT]: 2023-11-08 23:04:39 Age [y:d:h:m:s]: 01:148:09:57:27
Block: 887474 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367267 RingCT/type: yes/0
Extra: 014422e915c6878185d707db09ce3ea5c553d87f7cb689134c2a4fa54b686522060211000000024b8f5122000000000000000000

1 output(s) for total of 0.703769160000 dcy

stealth address amount amount idx
00: 238431ec3318800a7b18be7e3b60e9b5b36f7732cb040616e0a46309c7aa0172 0.703769160000 1343359 of 0

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": 887484, "vin": [ { "gen": { "height": 887474 } } ], "vout": [ { "amount": 703769160, "target": { "key": "238431ec3318800a7b18be7e3b60e9b5b36f7732cb040616e0a46309c7aa0172" } } ], "extra": [ 1, 68, 34, 233, 21, 198, 135, 129, 133, 215, 7, 219, 9, 206, 62, 165, 197, 83, 216, 127, 124, 182, 137, 19, 76, 42, 79, 165, 75, 104, 101, 34, 6, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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