← previous blocknext block →recent activity
Analyzing
Block #106,387,981
25 transactions · 22 stateful · 2026-09-20 06:09:42 UTC
Parallelism
72/100
Blocked
50%
Avg conflicts / tx
1.28
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,387,981 · 25 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
1w02w13w25w17w08w110w111w216w317w418w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdac9c1bc…c189
0x34b655…2a6f
14 touches
21 conflicts
0x36d7075f…d5c9
0x34b655…2a6f
14 touches
21 conflicts
0xcd9ba26b…108d
0x34b655…2a6f
14 touches
21 conflicts
0x9c2fc330…0091
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…002a
0x1b6862…e19c
6 touches
3 conflicts
0xd18a8dca…452b
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x0dd3d3cd…7281
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 0xdac9c1bc90…2ec189
Audit this contract →
← previous block·next block →recent activity