← previous blocknext block →recent activity
Analyzing
Block #109,143,310
14 transactions · 14 stateful · 2026-09-29 21:28:18 UTC
Parallelism
57/100
Blocked
43%
Avg conflicts / tx
1.14
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #109,143,310 · 14 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
4w05w16w27w38w49w511w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1032f16c…a9b1
0x34b655…2a6f
12 touches
15 conflicts
0x21bce2a9…2469
0x34b655…2a6f
12 touches
15 conflicts
0x3243e72f…1f6d
0x34b655…2a6f
12 touches
15 conflicts
0x500e6948…adc3
0x34b655…2a6f
12 touches
15 conflicts
0x5969523e…5191
0x34b655…2a6f
12 touches
15 conflicts
0x654dbfd0…02c9
0x34b655…2a6f
12 touches
15 conflicts
0x7499cc33…a306
0x34b655…2a6f
12 touches
15 conflicts
0x7d9ef283…ddd1
0x34b655…2a6f
12 touches
15 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 0x1032f16c0e…4fa9b1
Audit this contract →
← previous block·next block →recent activity