← previous blocknext block →recent activity
Analyzing
Block #86,258,671
17 transactions · 17 stateful · 2026-07-07 19:51:36 UTC
Parallelism
82/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,258,671 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w07w110w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6ce2feef…fee1
0x34b655…2a6f
4 touches
1 conflict
0x7c524e26…54c6
0x34b655…2a6f
4 touches
1 conflict
0xa6b89ebb…a66e
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xd93edb3f…94ec
0x34b655…2a6f
4 touches
1 conflict
0xd99b3b64…1c95
0x34b655…2a6f
4 touches
1 conflict
0x28ceceef…ecc2
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
1 conflict on slot 0x6ce2feef2b…d2fee1
Audit this contract →
← previous block·next block →recent activity