← previous blocknext block →recent activity
Analyzing
Block #106,959,152
25 transactions · 22 stateful · 2026-09-22 06:05:28 UTC
Parallelism
80/100
Blocked
32%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,959,152 · 25 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
3w05w08w19w215w016w318w119w120w423w024w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4258747a…8216
0x34b655…2a6f
10 touches
10 conflicts
0xcb21158b…f18d
0x34b655…2a6f
6 touches
3 conflicts
0x1d81790c…b9f7
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x7462b8f2…6312
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
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
10 conflicts on slot 0x4258747aa9…4b8216
Audit this contract →
← previous block·next block →recent activity