← previous blocknext block →recent activity
Analyzing
Block #106,543,615
14 transactions · 14 stateful · 2026-09-20 19:13:01 UTC
Parallelism
64/100
Blocked
50%
Avg conflicts / tx
1.29
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,543,615 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w08w110w111w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbc8fb280…76a3
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x656c2ba5…d35b
0x34b655…2a6f
8 touches
6 conflicts
0x4ae38164…15f0
0x34b655…2a6f
6 touches
3 conflicts
0x5ad5e6de…e7ad
0x34b655…2a6f
6 touches
3 conflicts
0x784f870c…0bfb
0x34b655…2a6f
6 touches
3 conflicts
0x90b49c59…4807
0x34b655…2a6f
6 touches
3 conflicts
0xa7d3cb90…e1d9
0x34b655…2a6f
6 touches
3 conflicts
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
10 conflicts on slot 0xbc8fb28081…2176a3
Audit this contract →
← previous block·next block →recent activity