← previous blocknext block →recent activity
Analyzing
Block #90,991,152
14 transactions · 13 stateful · 2026-07-28 06:52:34 UTC
Parallelism
79/100
Blocked
23%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,991,152 · 14 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
5w06w08w19w212w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf58ef399…86dc
0x34b655…2a6f
4 touches
1 conflict
0x72ed31c7…de4d
0x34b655…2a6f
4 touches
1 conflict
0x7527177c…0520
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0xcf501ad8…99ed
0x34b655…2a6f
4 touches
1 conflict
0xe34ea13e…dc16
0x34b655…2a6f
4 touches
1 conflict
0xec2a8d79…70cb
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 0xf58ef39910…0e86dc
Audit this contract →
← previous block·next block →recent activity