← previous blocknext block →recent activity
Analyzing
Block #106,539,120
27 transactions · 26 stateful · 2026-09-20 18:50:24 UTC
Parallelism
78/100
Blocked
42%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,539,120 · 27 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w15w26w113w316w217w318w422w224w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa3ed5a09…c6d3
0x34b655…2a6f
8 touches
6 conflicts
0xec2a8d79…70cb
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x38c6ff01…689f
0x34b655…2a6f
8 touches
6 conflicts
0x3e6302c8…64f5
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x6b267bdf…b173
0x34b655…2a6f
8 touches
6 conflicts
0x791e9200…9573
0x34b655…2a6f
8 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: Perpl
6 conflicts on slot 0xa3ed5a0966…25c6d3
Audit this contract →
← previous block·next block →recent activity