← previous blocknext block →recent activity
Analyzing
Block #106,429,871
12 transactions · 11 stateful · 2026-09-20 09:40:30 UTC
Parallelism
67/100
Blocked
36%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,429,871 · 12 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
2w07w18w29w311w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaee4f79…d6ee
0x34b655…2a6f
6 touches
3 conflicts
0x7cbbdd3f…65b0
0x34b655…2a6f
4 touches
1 conflict
0x9c088939…ddd7
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xb75367ff…a2b7
0x34b655…2a6f
4 touches
1 conflict
0xd29e547b…a1dd
0x34b655…2a6f
4 touches
1 conflict
0xe21234e7…bded
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
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
3 conflicts on slot 0xfaee4f79f9…06d6ee
Audit this contract →
← previous block·next block →recent activity