← previous blocknext block →recent activity
Analyzing
Block #108,533,291
36 transactions · 25 stateful · 2026-09-27 18:10:52 UTC
Parallelism
78/100
Blocked
56%
Avg conflicts / tx
1.22
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #108,533,291 · 36 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
1w02w13w26w38w09w111w212w313w415w516w627w428w534w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5086c64a…28ba
0x34b655…2a6f
14 touches
21 conflicts
0xd6a7469a…4fe8
0x34b655…2a6f
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0x68292fe7…d918
0x34b655…2a6f
10 touches
10 conflicts
0x75f928fc…0465
0x34b655…2a6f
10 touches
10 conflicts
0x78c305da…2c9a
0x34b655…2a6f
10 touches
10 conflicts
0x9cc778a3…2452
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
21 conflicts on slot 0x5086c64a56…bb28ba
Audit this contract →
← previous block·next block →recent activity