← previous blocknext block →recent activity
Analyzing
Block #90,460,519
10 transactions · 8 stateful · 2026-07-26 10:22:56 UTC
Parallelism
60/100
Blocked
38%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,460,519 · 10 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
0xac8a5059…fd42
0x34b655…2a6f
6 touches
3 conflicts
0x2e19029d…72a7
0x34b655…2a6f
4 touches
1 conflict
0x14c4e3ca…edda
0x34b655…2a6f
4 touches
1 conflict
0x14c4e3ca…edd9
0x34b655…2a6f
4 touches
1 conflict
0x818e1296…f4d7
0x34b655…2a6f
4 touches
1 conflict
0x0fe1e6e0…f553
0x34b655…2a6f
2 touches
0 conflicts
0x1683d146…5ec2
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
6 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity