← previous blocknext block →recent activity
Analyzing
Block #105,922,283
27 transactions · 20 stateful · 2026-09-18 15:05:45 UTC
Parallelism
85/100
Blocked
30%
Avg conflicts / tx
0.37
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,922,283 · 27 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w09w010w115w118w020w123w224w326w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa5f71148…62ee
0x40c49f…2af0
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x375b6201…9c1e
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x3002a0e5…0d32
0x34b655…2a6f
4 touches
1 conflict
0x3018a378…d7bb
0x34b655…2a6f
4 touches
1 conflict
0x3439deb5…2fa4
0x40c49f…2af0
4 touches
1 conflict
0x80398c66…f3cc
0x34b655…2a6f
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: 0x40c49f17…d22af0
3 conflicts on slot 0xa5f7114836…0662ee
Audit this contract →
← previous block·next block →recent activity