← previous blocknext block →recent activity
Analyzing
Block #90,484,001
11 transactions · 11 stateful · 2026-07-26 12:21:08 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,484,001 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xbde9cde5…4cff
0x34b655…2a6f
6 touches
3 conflicts
0x2170bea4…4722
0x34b655…2a6f
4 touches
1 conflict
0x2170bea4…4723
0x34b655…2a6f
4 touches
1 conflict
0x236dd751…aa8a
0x34b655…2a6f
4 touches
1 conflict
0x236dd751…aa8b
0x34b655…2a6f
4 touches
1 conflict
0x2616c789…84d0
0x34b655…2a6f
4 touches
1 conflict
0x3bb514bf…2967
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
6 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity