← previous blocknext block →recent activity
Analyzing
Block #106,215,824
21 transactions · 21 stateful · 2026-09-19 15:43:16 UTC
Parallelism
67/100
Blocked
48%
Avg conflicts / tx
1.24
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,215,824 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w16w29w110w011w112w013w115w217w318w419w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb7af7ea3…7d7d
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x746bcce3…d0ce
0x34b655…2a6f
8 touches
6 conflicts
0x206f4379…e08a
0x34b655…2a6f
8 touches
6 conflicts
0x358e10b7…2618
0x34b655…2a6f
8 touches
6 conflicts
0x4ee040ff…6373
0x34b655…2a6f
8 touches
6 conflicts
0xfbabb02d…af07
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
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 0xb7af7ea38f…ad7d7d
Audit this contract →
← previous block·next block →recent activity