← previous blocknext block →recent activity
Analyzing
Block #90,946,922
10 transactions · 8 stateful · 2026-07-28 03:10:00 UTC
Parallelism
80/100
Blocked
13%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,946,922 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x758a0dd5…0f46
0x34b655…2a6f
4 touches
1 conflict
0x9775559a…a8ec
0x34b655…2a6f
4 touches
1 conflict
0xcdaecd28…ab7b
0x34b655…2a6f
4 touches
1 conflict
0x7bacbc81…aa83
0x34b655…2a6f
3 touches
1 conflict
0x20067ecb…0e41
0x34b655…2a6f
2 touches
0 conflicts
0x23e706b3…0e16
0x34b655…2a6f
2 touches
0 conflicts
0x4c3a08af…03e1
0x34b655…2a6f
2 touches
0 conflicts
0x4d3eebe6…a3da
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
1 conflict on slot 0x758a0dd50c…2a0f46
Audit this contract →
← previous block·next block →recent activity