← previous blocknext block →recent activity
Analyzing
Block #86,711,413
21 transactions · 15 stateful · 2026-07-09 22:18:53 UTC
Parallelism
76/100
Blocked
40%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,711,413 · 21 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
4w05w16w19w010w214w118w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa7013be2…c0a8
0x34b655…2a6f
10 touches
10 conflicts
0x61d6f6e7…87d6
0x34b655…2a6f
6 touches
3 conflicts
0x4caf91f9…8ab5
0x34b655…2a6f
4 touches
1 conflict
0x5238dcb7…e0e2
0x34b655…2a6f
4 touches
1 conflict
0x70ff9262…8d80
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xa7da2810…dfcb
0x34b655…2a6f
4 touches
1 conflict
0xa92c8763…6d7f
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
10 conflicts on slot 0xa7013be2a1…9ac0a8
Audit this contract →
← previous block·next block →recent activity