← previous blocknext block →recent activity
Analyzing
Block #108,627,337
51 transactions · 46 stateful · 2026-09-28 02:04:31 UTC
Parallelism
67/100
Blocked
67%
Avg conflicts / tx
2.49
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #108,627,337 · 51 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w07w18w210w111w312w419w320w421w522w623w724w825w927w1028w1132w435w537w641w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
22 touches
55 conflicts
0x724ba0cf…01c7
0x34b655…2a6f
14 touches
21 conflicts
0xc16c9d9e…a0a3
0xd32edf…ff58
13 touches
21 conflicts
0x309f47c0…e1cf
0x34b655…2a6f
12 touches
15 conflicts
0x3243e72f…1f6d
0x34b655…2a6f
12 touches
15 conflicts
0x3b65c5ca…9f83
0x34b655…2a6f
12 touches
15 conflicts
0x434ddf72…de6a
0x34b655…2a6f
12 touches
15 conflicts
0x5969523e…5191
0x34b655…2a6f
12 touches
15 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
55 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity