← previous blocknext block →recent activity
Analyzing
Block #108,466,800
24 transactions · 17 stateful · 2026-09-27 12:36:09 UTC
Parallelism
67/100
Blocked
47%
Avg conflicts / tx
1.17
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #108,466,800 · 24 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
1w03w15w27w39w412w515w522w623w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1c4e5ce…0dec
0x34b655…2a6f
12 touches
15 conflicts
0x659933ab…e189
0x34b655…2a6f
12 touches
15 conflicts
0xfcd5e68f…2a12
0x34b655…2a6f
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x945d1dbe…e1d7
0xc8689a…ee79
10 touches
10 conflicts
0x6d5d1fb5…86a7
0x34b655…2a6f
8 touches
6 conflicts
0x7006165a…df17
0x34b655…2a6f
8 touches
6 conflicts
0x7efbf74f…f9d2
0x34b655…2a6f
8 touches
6 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 0xe1c4e5ce15…770dec
Audit this contract →
← previous block·next block →recent activity