← previous blocknext block →recent activity
Analyzing
Block #85,992,390
29 transactions · 23 stateful · 2026-07-06 14:13:44 UTC
Parallelism
83/100
Blocked
43%
Avg conflicts / tx
0.55
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,992,390 · 29 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w211w015w017w118w119w124w125w226w327w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xcb89a818…e7c1
0x34b655…2a6f
6 touches
3 conflicts
0x5ed9837b…2c26
0xd32edf…ff58
5 touches
3 conflicts
0x3e8c7016…0c69
0x34b655…2a6f
4 touches
1 conflict
0x46128aa0…07d8
0x34b655…2a6f
4 touches
1 conflict
0x463be44a…2830
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xb409e204…89ac
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity