← previous blocknext block →recent activity
Analyzing
Block #108,796,147
22 transactions · 18 stateful · 2026-09-28 16:14:52 UTC
Parallelism
68/100
Blocked
72%
Avg conflicts / tx
2.05
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #108,796,147 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w16w27w39w010w111w215w417w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa02838a3…bc54
0x34b655…2a6f
12 touches
15 conflicts
0xea02471d…1542
0x34b655…2a6f
12 touches
15 conflicts
0x1c389468…6b0e
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0x199a4f01…2183
0x34b655…2a6f
10 touches
10 conflicts
0x1b5d2e60…99b5
0x34b655…2a6f
10 touches
10 conflicts
0x1eb0fab5…3517
0x34b655…2a6f
10 touches
10 conflicts
0x366a19b0…f065
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 0xa02838a385…ffbc54
Audit this contract →
← previous block·next block →recent activity