← previous blocknext block →recent activity
Analyzing
Block #108,565,264
18 transactions · 15 stateful · 2026-09-27 20:52:02 UTC
Parallelism
78/100
Blocked
47%
Avg conflicts / tx
0.78
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,565,264 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w18w09w111w214w017w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xe1aed979…dee5
0xd32edf…ff58
7 touches
6 conflicts
0x1127d8e0…3291
0x34b655…2a6f
4 touches
1 conflict
0x27909bb7…b461
0x34b655…2a6f
4 touches
1 conflict
0x2d405026…6d9f
0x34b655…2a6f
4 touches
1 conflict
0x39eca8fb…c49a
0x34b655…2a6f
4 touches
1 conflict
0x3fa1fac4…826c
0x34b655…2a6f
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
6 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity