← previous blocknext block →recent activity
Analyzing
Block #107,440,811
11 transactions · 11 stateful · 2026-09-23 22:30:16 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #107,440,811 · 11 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
2w03w14w25w39w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x24c5620c…7ac5
0x34b655…2a6f
6 touches
3 conflicts
0xe9693c23…43cc
0x34b655…2a6f
6 touches
3 conflicts
0x199a4f01…2183
0x34b655…2a6f
5 touches
3 conflicts
0x8a35acfb…d1b1
0x37db7f…ec7b
5 touches
3 conflicts
0x8a35acfb…d1b0
0x37db7f…ec7b
5 touches
3 conflicts
0xfcdb5918…2b49
0x34b655…2a6f
4 touches
1 conflict
0xb8dc136f…fb16
0xc8689a…ee79
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: Perpl
6 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity