← previous blocknext block →recent activity
Analyzing
Block #108,510,051
28 transactions · 24 stateful · 2026-09-27 16:13:54 UTC
Parallelism
71/100
Blocked
50%
Avg conflicts / tx
1.25
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #108,510,051 · 28 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
1w02w03w05w18w09w112w113w214w315w416w117w224w525w627w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5dc501b…831c
0x34b655…2a6f
14 touches
21 conflicts
0x7bd229ad…63b2
0x34b655…2a6f
14 touches
21 conflicts
0x3c0e1339…778a
0xd32edf…ff58
7 touches
6 conflicts
0xdced4209…6afa
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…001d
0x1b6862…e19c
6 touches
3 conflicts
0xcb45d9d6…cb85
0x1b6862…e19c
6 touches
3 conflicts
0x235bbb77…89ea
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 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
21 conflicts on slot 0xf5dc501bf7…74831c
Audit this contract →
← previous block·next block →recent activity