← previous blocknext block →recent activity
Analyzing
Block #90,625,125
22 transactions · 20 stateful · 2026-07-27 00:11:01 UTC
Parallelism
86/100
Blocked
15%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,625,125 · 22 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
6w07w08w118w220w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fd0b86c…b37c
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xfc3d5171…8357
0x34b655…2a6f
4 touches
1 conflict
0x53f7214d…8ec6
0x34b655…2a6f
4 touches
1 conflict
0xcffc17bc…3544
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
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 0x6fd0b86c31…77b37c
Audit this contract →
← previous block·next block →recent activity