← previous blocknext block →recent activity
Analyzing
Block #108,626,794
31 transactions · 24 stateful · 2026-09-28 02:01:47 UTC
Parallelism
74/100
Blocked
54%
Avg conflicts / tx
1.42
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #108,626,794 · 31 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
1w02w13w26w07w18w29w310w412w529w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x724ba0cf…01c7
0x34b655…2a6f
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0x945d1dbe…e1d7
0xc8689a…ee79
12 touches
15 conflicts
0x03624810…e26d
0x34b655…2a6f
10 touches
10 conflicts
0x16d77246…bac5
0x34b655…2a6f
10 touches
10 conflicts
0x280aaa58…1c52
0x34b655…2a6f
10 touches
10 conflicts
0x309f47c0…e1cf
0x34b655…2a6f
10 touches
10 conflicts
0x3243e72f…1f6d
0x34b655…2a6f
10 touches
10 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 0x724ba0cf22…b301c7
Audit this contract →
← previous block·next block →recent activity