← previous blocknext block →recent activity
Analyzing
Block #108,649,751
23 transactions · 21 stateful · 2026-09-28 03:57:26 UTC
Parallelism
74/100
Blocked
52%
Avg conflicts / tx
1.04
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,649,751 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w06w07w110w011w112w213w314w415w516w117w118w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd0872e23…a157
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x3fa1fac4…826c
0x34b655…2a6f
6 touches
3 conflicts
0x4626aa4a…50e9
0xd32edf…ff58
5 touches
3 conflicts
0x580c6fe7…0fe9
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
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
10 conflicts on slot 0xd0872e2395…4ca157
Audit this contract →
← previous block·next block →recent activity