← previous blocknext block →recent activity
Analyzing
Block #106,031,520
18 transactions · 18 stateful · 2026-09-19 00:15:42 UTC
Parallelism
72/100
Blocked
39%
Avg conflicts / tx
0.72
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,031,520 · 18 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
1w02w14w06w17w08w110w011w112w213w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x03f6cbe2…ba74
0x6f6493…b480
10 touches
10 conflicts
0x0db0b764…9cc8
0x6f6493…b480
10 touches
10 conflicts
0x1654b46a…067a
0x6f6493…b480
10 touches
10 conflicts
0x172ee3b5…a860
0x6f6493…b480
10 touches
10 conflicts
0x2072e1dc…342c
0x6f6493…b480
10 touches
10 conflicts
0x23d50ab1…b0d8
0x6f6493…b480
10 touches
10 conflicts
0x2a7ba97c…e90e
0x6f6493…b480
10 touches
10 conflicts
0x3ec45fc1…502d
0x6f6493…b480
10 touches
10 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
10 conflicts on slot 0x03f6cbe27b…22ba74
Audit this contract →
← previous block·next block →recent activity