← previous blocknext block →recent activity
Analyzing
Block #108,366,244
21 transactions · 20 stateful · 2026-09-27 04:10:04 UTC
Parallelism
71/100
Blocked
45%
Avg conflicts / tx
1.14
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,366,244 · 21 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
1w02w13w24w35w06w17w212w013w417w319w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbc8fb280…76a3
0x34b655…2a6f
12 touches
15 conflicts
0xb5cdcafb…51e2
0x34b655…2a6f
10 touches
10 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xfdb6a6c8…31c4
0x34b655…2a6f
10 touches
10 conflicts
0x9daafdf9…bb53
0x34b655…2a6f
8 touches
6 conflicts
0xb8a4b8a7…e631
0x34b655…2a6f
8 touches
6 conflicts
0xd874dcbe…381c
0x34b655…2a6f
8 touches
6 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 0xbc8fb28081…2176a3
Audit this contract →
← previous block·next block →recent activity