← previous blocknext block →recent activity
Analyzing
Block #108,939,976
22 transactions · 20 stateful · 2026-09-29 04:21:56 UTC
Parallelism
77/100
Blocked
55%
Avg conflicts / tx
0.91
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,939,976 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w08w19w110w111w212w313w418w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x57e4c370…3b32
0x34b655…2a6f
8 touches
6 conflicts
0xd723328e…1d38
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0xfac61869…a560
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbff401a6…b269
0x1b6862…e19c
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 0x57e4c370e0…043b32
Audit this contract →
← previous block·next block →recent activity