← previous blocknext block →recent activity
Analyzing
Block #106,308,079
24 transactions · 16 stateful · 2026-09-19 23:27:34 UTC
Parallelism
88/100
Blocked
31%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,308,079 · 24 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w07w013w117w018w119w220w221w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xadccc35d…5a2d
0x34b655…2a6f
6 touches
3 conflicts
0x085df2c1…305a
0x34b655…2a6f
6 touches
3 conflicts
0x65903ef9…2567
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x366a19b0…f065
0x34b655…2a6f
4 touches
1 conflict
0x4c0447dd…298b
0x34b655…2a6f
4 touches
1 conflict
0x612b5b5d…78b9
0x34b655…2a6f
4 touches
1 conflict
0x75f928fc…0465
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
3 conflicts on slot 0xadccc35dd1…435a2d
Audit this contract →
← previous block·next block →recent activity