Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c578c45c201528bdc3aef8943f2d755f8d9d9799f18db10a08f79971164bef2e

Tx prefix hash: 943a3d966edd85adb15661a41f6fd509cd612755d9ab2b3fcec886ffa6e9a84c
Tx public key: 09cd0f8f23f56cc93d9ae4205c70d1b00bf6aa91de69cc50b72647d1b84be1c4
Timestamp: 1696102521 Timestamp [UCT]: 2023-09-30 19:35:21 Age [y:d:h:m:s]: 01:103:22:16:00
Block: 859637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 335546 RingCT/type: yes/0
Extra: 0109cd0f8f23f56cc93d9ae4205c70d1b00bf6aa91de69cc50b72647d1b84be1c40211000000084b8f5122000000000000000000

1 output(s) for total of 0.870293639000 dcy

stealth address amount amount idx
00: db50cd1249590a0093b7672ac3151ec1c4739690cef48bdff9875bc881ca0697 0.870293639000 1313871 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": 859647, "vin": [ { "gen": { "height": 859637 } } ], "vout": [ { "amount": 870293639, "target": { "key": "db50cd1249590a0093b7672ac3151ec1c4739690cef48bdff9875bc881ca0697" } } ], "extra": [ 1, 9, 205, 15, 143, 35, 245, 108, 201, 61, 154, 228, 32, 92, 112, 209, 176, 11, 246, 170, 145, 222, 105, 204, 80, 183, 38, 71, 209, 184, 75, 225, 196, 2, 17, 0, 0, 0, 8, 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