← previous blocknext block →recent activity
Analyzing
Block #106,155,718
16 transactions · 16 stateful · 2026-09-19 10:40:44 UTC
Parallelism
63/100
Blocked
38%
Avg conflicts / tx
0.88
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,155,718 · 16 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
5w07w18w29w310w311w412w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3e1d11e9…61de
0x34b655…2a6f
10 touches
10 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
6 touches
3 conflicts
0x4ec9ff52…e6f7
0x34b655…2a6f
6 touches
3 conflicts
0x9ff4ca89…6115
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x9430e759…86df
0x34b655…2a6f
4 touches
1 conflict
0x00216970…a965
0x34b655…2a6f
4 touches
1 conflict
0x566d7924…8385
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 0x3e1d11e9a7…8861de
Audit this contract →
← previous block·next block →recent activity