← previous blocknext block →recent activity
Analyzing
Block #108,335,709
38 transactions · 29 stateful · 2026-09-27 01:36:24 UTC
Parallelism
79/100
Blocked
55%
Avg conflicts / tx
1.11
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #108,335,709 · 38 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
2w05w17w29w311w413w532w535w636w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x34dad526…5f98
0x34b655…2a6f
12 touches
15 conflicts
0xfcd5e68f…2a12
0x34b655…2a6f
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0xe226a0be…c046
0x34b655…2a6f
12 touches
15 conflicts
0x6d5d1fb5…86a7
0x34b655…2a6f
10 touches
10 conflicts
0x7006165a…df17
0x34b655…2a6f
10 touches
10 conflicts
0x76832384…dc5b
0x34b655…2a6f
10 touches
10 conflicts
0x9daafdf9…bb53
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
15 conflicts on slot 0x34dad526d0…1d5f98
Audit this contract →
← previous block·next block →recent activity