← previous blocknext block →recent activity
Analyzing
Block #90,437,194
9 transactions · 9 stateful · 2026-07-26 08:25:02 UTC
Parallelism
78/100
Blocked
11%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,437,194 · 9 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x0a906ba5…2454
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x91b0f8ed…6bd7
0x34b655…2a6f
4 touches
1 conflict
0x0a6e8942…fd6a
0x34b655…2a6f
2 touches
0 conflicts
0x0a6e8942…fd6b
0x34b655…2a6f
2 touches
0 conflicts
0x757b0543…e087
0x34b655…2a6f
2 touches
0 conflicts
0x7c7eff13…16db
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity