← previous blocknext block →recent activity
Analyzing
Block #106,959,338
21 transactions · 19 stateful · 2026-09-22 06:06:24 UTC
Parallelism
86/100
Blocked
37%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,959,338 · 21 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
1w03w04w16w17w08w110w011w114w015w216w017w120w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1d81790c…b9f7
0x34b655…2a6f
6 touches
3 conflicts
0x4bb82af5…2aba
0x34b655…2a6f
4 touches
1 conflict
0x51aa664e…d3b8
0x34b655…2a6f
4 touches
1 conflict
0xa95f0b7a…b60a
0x34b655…2a6f
4 touches
1 conflict
0xfcd5e68f…2a12
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x00000000…004b
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
3 conflicts on slot 0x1d81790c4e…7cb9f7
Audit this contract →
← previous block·next block →recent activity