← previous blocknext block →recent activity
Analyzing
Block #90,297,382
25 transactions · 24 stateful · 2026-07-25 20:29:01 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.16
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,297,382 · 25 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
1w02w120w022w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xbcab7dbe…2825
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xf28ee159…1f3b
0x34b655…2a6f
4 touches
1 conflict
0xf394e6ad…f568
0x34b655…2a6f
4 touches
1 conflict
0x04e8de25…7424
0x34b655…2a6f
2 touches
0 conflicts
0x07907555…e12e
0x34b655…2a6f
2 touches
0 conflicts
0x08c5649d…b936
0x34b655…2a6f
2 touches
0 conflicts
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity