← previous blocknext block →recent activity
Analyzing
Block #90,866,885
9 transactions · 9 stateful · 2026-07-27 20:27:24 UTC
Parallelism
56/100
Blocked
44%
Avg conflicts / tx
0.78
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,866,885 · 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
1w02w13w24w38w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x152f8e3d…3da0
0x34b655…2a6f
6 touches
3 conflicts
0x663ab2c3…67ab
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x27034002…2f27
0x34b655…2a6f
6 touches
3 conflicts
0x6ae4a85e…c097
0x34b655…2a6f
4 touches
1 conflict
0x9efbd42c…c1bb
0x34b655…2a6f
4 touches
1 conflict
0xa524a39b…df24
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