← previous blocknext block →recent activity
Analyzing
Block #106,190,316
20 transactions · 19 stateful · 2026-09-19 13:34:50 UTC
Parallelism
75/100
Blocked
37%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,190,316 · 20 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
1w02w13w24w35w414w015w116w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x03264d6f…8e17
0x6f6493…b480
7 touches
6 conflicts
0x047e0391…44de
0x6f6493…b480
7 touches
6 conflicts
0x07f2a400…9865
0x6f6493…b480
7 touches
6 conflicts
0x0850b78e…6494
0x6f6493…b480
7 touches
6 conflicts
0x09c39ba2…aa8e
0x6f6493…b480
7 touches
6 conflicts
0x0fc95e7c…99e2
0x6f6493…b480
7 touches
6 conflicts
0x1dfa419c…bdfe
0x6f6493…b480
7 touches
6 conflicts
0x23ec6bd4…7417
0x6f6493…b480
7 touches
6 conflicts
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: 0x6f6493e3…08b480
6 conflicts on slot 0x03264d6fef…6b8e17
Audit this contract →
← previous block·next block →recent activity