← previous blocknext block →recent activity
Analyzing
Block #90,962,632
14 transactions · 14 stateful · 2026-07-28 04:29:00 UTC
Parallelism
79/100
Blocked
36%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,962,632 · 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
1w02w13w04w16w07w110w213w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x957c875f…b3f9
0x34b655…2a6f
4 touches
1 conflict
0x9a6bc012…7495
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xcedd9c7b…916e
0x34b655…2a6f
4 touches
1 conflict
0xd35783e3…c38a
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x1cdfe548…d3aa
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 0x957c875f2a…99b3f9
Audit this contract →
← previous block·next block →recent activity