← previous blocknext block →recent activity
Analyzing
Block #108,498,866
18 transactions · 18 stateful · 2026-09-27 15:17:35 UTC
Parallelism
56/100
Blocked
56%
Avg conflicts / tx
1.89
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #108,498,866 · 18 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
1w02w03w14w25w36w411w114w415w516w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1c4e5ce…0dec
0x34b655…2a6f
16 touches
28 conflicts
0x4c29ecd5…58b6
0x34b655…2a6f
14 touches
21 conflicts
0x3db01639…a6bd
0x34b655…2a6f
12 touches
15 conflicts
0x26471102…35f9
0x34b655…2a6f
12 touches
15 conflicts
0x40d6d1e9…131e
0x34b655…2a6f
10 touches
10 conflicts
0x3243e72f…1f6d
0x34b655…2a6f
10 touches
10 conflicts
0x90f65937…f295
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
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
28 conflicts on slot 0xe1c4e5ce15…770dec
Audit this contract →
← previous block·next block →recent activity