← previous blocknext block →recent activity
Analyzing
Block #90,237,510
9 transactions · 9 stateful · 2026-07-25 15:26:14 UTC
Parallelism
56/100
Blocked
33%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,237,510 · 9 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
4w05w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x2bad40ae…0522
0x34b655…2a6f
4 touches
1 conflict
0x2bad40ae…0523
0x34b655…2a6f
4 touches
1 conflict
0x306233f2…96c3
0x34b655…2a6f
4 touches
1 conflict
0x3cd30154…5939
0x34b655…2a6f
4 touches
1 conflict
0x49d544eb…9d13
0x34b655…2a6f
4 touches
1 conflict
0x4f394483…ff62
0x34b655…2a6f
4 touches
1 conflict
0x5e32f9d6…43bc
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