← previous blocknext block →recent activity
Analyzing
Block #86,757,312
26 transactions · 21 stateful · 2026-07-10 03:25:44 UTC
Parallelism
81/100
Blocked
52%
Avg conflicts / tx
0.88
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,757,312 · 26 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
2w03w16w07w19w011w112w213w314w415w116w219w320w424w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0xc3688185…9b36
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x2c8bf7d9…3cc7
0xc8689a…ee79
6 touches
3 conflicts
0x1da60af2…3010
0x34b655…2a6f
6 touches
3 conflicts
0x4abe1e75…af7b
0x34b655…2a6f
6 touches
3 conflicts
0x5b9e5ecc…2bc7
0x34b655…2a6f
6 touches
3 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 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity