← previous blocknext block →recent activity
Analyzing
Block #106,476,736
20 transactions · 20 stateful · 2026-09-20 13:36:25 UTC
Parallelism
80/100
Blocked
30%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,476,736 · 20 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
1w02w13w14w25w06w117w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9dd0a735…4d04
0x34b655…2a6f
8 touches
6 conflicts
0x9d796412…aacc
0x34b655…2a6f
8 touches
6 conflicts
0xecd87a39…d9c5
0x34b655…2a6f
8 touches
6 conflicts
0xf77fbd5a…8833
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0x3d93ad2c…e747
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0xfdd131fa…dbdb
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
6 conflicts on slot 0x9dd0a735d4…464d04
Audit this contract →
← previous block·next block →recent activity