← previous blocknext block →recent activity
Analyzing
Block #106,568,161
16 transactions · 13 stateful · 2026-09-20 21:16:33 UTC
Parallelism
75/100
Blocked
31%
Avg conflicts / tx
0.31
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,568,161 · 16 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
1w02w13w14w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x88e771e8…7d4a
0x34b655…2a6f
4 touches
1 conflict
0x2130a548…c1de
0x34b655…2a6f
4 touches
1 conflict
0xb2560305…f27d
0x34b655…2a6f
4 touches
1 conflict
0xba1edffb…323e
0x34b655…2a6f
4 touches
1 conflict
0xc6615a36…3cf0
0x34b655…2a6f
4 touches
1 conflict
0xd7d44415…a1d3
0x34b655…2a6f
4 touches
1 conflict
0x49b9fdd5…9c16
0x34b655…2a6f
4 touches
1 conflict
0xe2265475…62e5
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: Perpl
1 conflict on slot 0x88e771e8ba…5c7d4a
Audit this contract →
← previous block·next block →recent activity