← previous blocknext block →recent activity
Analyzing
Block #109,236,187
21 transactions · 17 stateful · 2026-09-30 05:16:09 UTC
Parallelism
71/100
Blocked
47%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #109,236,187 · 21 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
1w02w03w14w25w38w410w514w415w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0x7d9ef283…ddd1
0x34b655…2a6f
10 touches
10 conflicts
0x945d1dbe…e1d7
0xc8689a…ee79
8 touches
6 conflicts
0x1032f16c…a9b1
0x34b655…2a6f
8 touches
6 conflicts
0x3243e72f…1f6d
0x34b655…2a6f
8 touches
6 conflicts
0x5969523e…5191
0x34b655…2a6f
8 touches
6 conflicts
0x6be03381…d26f
0x34b655…2a6f
8 touches
6 conflicts
0xe21f9645…ce5f
0x34b655…2a6f
8 touches
6 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
15 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity