← previous blocknext block →recent activity
Analyzing
Block #106,539,584
17 transactions · 15 stateful · 2026-09-20 18:52:44 UTC
Parallelism
65/100
Blocked
33%
Avg conflicts / tx
0.71
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,539,584 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w010w111w212w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcf54cdd6…9ce3
0x34b655…2a6f
10 touches
10 conflicts
0x3b6e959d…158f
0x34b655…2a6f
8 touches
6 conflicts
0x2c2db8e9…fdc7
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x4fe9d545…ac43
0x34b655…2a6f
6 touches
3 conflicts
0x2a2896a0…2a0a
0x34b655…2a6f
4 touches
1 conflict
0x8c6be8fe…7a2f
0x34b655…2a6f
4 touches
1 conflict
0x93f709d7…11e6
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
10 conflicts on slot 0xcf54cdd6d3…a29ce3
Audit this contract →
← previous block·next block →recent activity