← previous blocknext block →recent activity
Analyzing
Block #106,567,817
34 transactions · 23 stateful · 2026-09-20 21:14:49 UTC
Parallelism
88/100
Blocked
35%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,567,817 · 34 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
1w03w14w15w06w17w28w39w022w228w131w033w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x39842dc9…d417
0x34b655…2a6f
8 touches
6 conflicts
0x375b6201…9c1e
0x34b655…2a6f
8 touches
6 conflicts
0x0463db49…5d05
0x34b655…2a6f
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xf6deafb5…5c25
0x34b655…2a6f
6 touches
3 conflicts
0x32c85e0d…8759
0x34b655…2a6f
4 touches
1 conflict
0x0dbf9688…c6cf
0xd18b7e…414b
4 touches
1 conflict
0xd2867a41…1976
0x065c9d…c394
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 0x39842dc95c…b7d417
Audit this contract →
← previous block·next block →recent activity