← previous blocknext block →recent activity
Analyzing
Block #90,839,150
16 transactions · 16 stateful · 2026-07-27 18:07:50 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,839,150 · 16 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
2w03w06w09w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9e1423e0…9c81
0x34b655…2a6f
4 touches
1 conflict
0x9fd372a1…a959
0x34b655…2a6f
4 touches
1 conflict
0xb951573a…4b20
0x34b655…2a6f
4 touches
1 conflict
0xb951573a…4b21
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xdb86d50f…b5fc
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5eb
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
1 conflict on slot 0x9e1423e073…2a9c81
Audit this contract →
← previous block·next block →recent activity