← previous blocknext block →recent activity
Analyzing
Block #106,191,754
31 transactions · 30 stateful · 2026-09-19 13:42:05 UTC
Parallelism
71/100
Blocked
43%
Avg conflicts / tx
1.61
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,191,754 · 31 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w19w112w213w214w315w417w518w619w420w721w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd41f5136…97c6
0x34b655…2a6f
14 touches
21 conflicts
0x0033014e…086d
0x34b655…2a6f
12 touches
15 conflicts
0x6280de8b…2e7c
0x34b655…2a6f
10 touches
10 conflicts
0x315e07b8…9823
0x34b655…2a6f
8 touches
6 conflicts
0x80398c66…f3cc
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0xf90c6521…d8f0
0x34b655…2a6f
6 touches
3 conflicts
0x019264d7…c75b
0x34b655…2a6f
6 touches
3 conflicts
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
21 conflicts on slot 0xd41f513688…4197c6
Audit this contract →
← previous block·next block →recent activity