← previous blocknext block →recent activity
Analyzing
Block #108,630,436
50 transactions · 45 stateful · 2026-09-28 02:20:08 UTC
Parallelism
62/100
Blocked
71%
Avg conflicts / tx
2.8
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #108,630,436 · 50 txs across 19 waves · depth 19
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
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w16w19w210w312w014w215w322w223w337w1041w1447w348w449w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
26 touches
78 conflicts
0x326a02b5…8dad
0x34b655…2a6f
18 touches
36 conflicts
0x6fbc2e5a…e69c
0x34b655…2a6f
18 touches
36 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
18 touches
36 conflicts
0x46c14e01…ff09
0x34b655…2a6f
18 touches
36 conflicts
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0xcb45d9d6…cb87
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…001f
0x1b6862…e19c
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
78 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity