← previous blocknext block →recent activity
Analyzing
Block #106,185,474
23 transactions · 20 stateful · 2026-09-19 13:10:29 UTC
Parallelism
83/100
Blocked
40%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,185,474 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w16w18w115w016w117w218w319w322w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xff4fd690…957d
0x34b655…2a6f
6 touches
3 conflicts
0x56409df0…27cd
0x34b655…2a6f
6 touches
3 conflicts
0x9167c873…748f
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x301e1c77…9e30
0x34b655…2a6f
4 touches
1 conflict
0x67a9f76d…0b84
0x34b655…2a6f
4 touches
1 conflict
0x67a9f76d…0b85
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
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 0xff4fd6901a…27957d
Audit this contract →
← previous block·next block →recent activity