← previous blocknext block →recent activity
Analyzing
Block #90,558,562
10 transactions · 9 stateful · 2026-07-26 18:36:10 UTC
Parallelism
70/100
Blocked
22%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,558,562 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
6 touches
3 conflicts
0xba1ef4c2…ef4e
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd00c33c6…f985
0x34b655…2a6f
4 touches
1 conflict
0xe8c70616…ed52
0x34b655…2a6f
4 touches
1 conflict
0xe8c70616…ed53
0x34b655…2a6f
4 touches
1 conflict
0x15336fe3…1f37
0x34b655…2a6f
4 touches
1 conflict
0x2fabfabb…f371
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 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity