← previous blocknext block →recent activity
Analyzing
Block #86,882,454
19 transactions · 17 stateful · 2026-07-10 17:22:10 UTC
Parallelism
68/100
Blocked
41%
Avg conflicts / tx
0.84
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,882,454 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w27w38w412w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9fbc6a76…9c29
0x34b655…2a6f
10 touches
10 conflicts
0xb9192ba2…d81a
0x34b655…2a6f
10 touches
10 conflicts
0xd56f5316…0b5a
0x34b655…2a6f
10 touches
10 conflicts
0xd1ec0dfd…ccc0
0xc8689a…ee79
10 touches
10 conflicts
0x1941b441…5889
0x34b655…2a6f
10 touches
10 conflicts
0x31519d10…f76b
0x34b655…2a6f
10 touches
10 conflicts
0x42aad825…b067
0x34b655…2a6f
10 touches
10 conflicts
0x44fc2746…0a53
0x34b655…2a6f
10 touches
10 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
10 conflicts on slot 0x9fbc6a765b…379c29
Audit this contract →
← previous block·next block →recent activity