← previous blocknext block →recent activity
Analyzing
Block #108,496,791
48 transactions · 40 stateful · 2026-09-27 15:07:09 UTC
Parallelism
63/100
Blocked
70%
Avg conflicts / tx
3.69
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #108,496,791 · 48 txs across 18 waves · depth 18
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w911w1016w1120w1221w1322w1423w1524w1625w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
34 touches
136 conflicts
0x945d1dbe…e1d7
0xc8689a…ee79
22 touches
55 conflicts
0x3243e72f…1f6d
0x34b655…2a6f
20 touches
45 conflicts
0x3db01639…a6bd
0x34b655…2a6f
20 touches
45 conflicts
0x40d6d1e9…131e
0x34b655…2a6f
20 touches
45 conflicts
0x4c29ecd5…58b6
0x34b655…2a6f
20 touches
45 conflicts
0x5969523e…5191
0x34b655…2a6f
20 touches
45 conflicts
0x7006165a…df17
0x34b655…2a6f
20 touches
45 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
136 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity