← previous blocknext block →recent activity
Analyzing
Block #109,228,886
19 transactions · 14 stateful · 2026-09-30 04:39:24 UTC
Parallelism
63/100
Blocked
50%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #109,228,886 · 19 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
1w02w16w27w312w216w417w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7d9ef283…ddd1
0x34b655…2a6f
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x3be6459e…270b
0x34b655…2a6f
6 touches
3 conflicts
0x469854ac…edcd
0x34b655…2a6f
6 touches
3 conflicts
0x5969523e…5191
0x34b655…2a6f
6 touches
3 conflicts
0x945d1dbe…e1d7
0xc8689a…ee79
6 touches
3 conflicts
0x3243e72f…1f6d
0x34b655…2a6f
6 touches
3 conflicts
0xe1c4e5ce…0dec
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
15 conflicts on slot 0x7d9ef2836a…01ddd1
Audit this contract →
← previous block·next block →recent activity