← previous blocknext block →recent activity
Analyzing
Block #108,285,816
19 transactions · 17 stateful · 2026-09-26 21:25:20 UTC
Parallelism
68/100
Blocked
41%
Avg conflicts / tx
0.89
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,285,816 · 19 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
1w02w13w24w35w46w07w19w514w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0x5969523e…5191
0x34b655…2a6f
10 touches
10 conflicts
0x5ad5e6de…e7ad
0x34b655…2a6f
10 touches
10 conflicts
0x7e4ebdbe…0e9f
0x34b655…2a6f
10 touches
10 conflicts
0x8e7fd942…c379
0x34b655…2a6f
10 touches
10 conflicts
0x9daafdf9…bb53
0x34b655…2a6f
10 touches
10 conflicts
0xa7d3cb90…e1d9
0x34b655…2a6f
10 touches
10 conflicts
0xa9371684…df38
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity