← previous blocknext block →recent activity
Analyzing
Block #109,176,182
25 transactions · 21 stateful · 2026-09-30 00:14:07 UTC
Parallelism
68/100
Blocked
33%
Avg conflicts / tx
1.16
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #109,176,182 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w624w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7d9ef283…ddd1
0x34b655…2a6f
16 touches
28 conflicts
0x16d77246…bac5
0x34b655…2a6f
14 touches
21 conflicts
0x280aaa58…1c52
0x34b655…2a6f
14 touches
21 conflicts
0x3243e72f…1f6d
0x34b655…2a6f
14 touches
21 conflicts
0x41eea7ab…3502
0x34b655…2a6f
14 touches
21 conflicts
0x5969523e…5191
0x34b655…2a6f
14 touches
21 conflicts
0x5b4c80c8…c242
0x34b655…2a6f
14 touches
21 conflicts
0x945d1dbe…e1d7
0xc8689a…ee79
14 touches
21 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
28 conflicts on slot 0x7d9ef2836a…01ddd1
Audit this contract →
← previous block·next block →recent activity