← previous blocknext block →recent activity
Analyzing
Block #106,954,590
32 transactions · 25 stateful · 2026-09-22 05:42:31 UTC
Parallelism
88/100
Blocked
44%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,954,590 · 32 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w07w19w210w011w115w016w117w218w323w024w026w127w228w130w031w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1f396cee…862f
0x34b655…2a6f
8 touches
6 conflicts
0xfd75192e…887a
0x34b655…2a6f
8 touches
6 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x95523e2a…4c01
0x065c9d…c394
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xd4e513d0…8445
0x065c9d…c394
5 touches
3 conflicts
0x00000000…004c
0x80c745…7210
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 0x1f396cee30…ac862f
Audit this contract →
← previous block·next block →recent activity