← previous blocknext block →recent activity
Analyzing
Block #106,810,079
34 transactions · 31 stateful · 2026-09-21 17:35:07 UTC
Parallelism
76/100
Blocked
48%
Avg conflicts / tx
1.38
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,810,079 · 34 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
1w02w13w04w15w26w216w317w418w421w124w426w527w628w733w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01f19c33…170d
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xa626f3da…1947
0x34b655…2a6f
8 touches
6 conflicts
0xd228502a…5e76
0x34b655…2a6f
8 touches
6 conflicts
0xcef70a96…db44
0x34b655…2a6f
6 touches
3 conflicts
0xb2560305…f27d
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 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 0x01f19c3396…f1170d
Audit this contract →
← previous block·next block →recent activity