← previous blocknext block →recent activity
Analyzing
Block #86,780,500
16 transactions · 12 stateful · 2026-07-10 06:00:28 UTC
Parallelism
88/100
Blocked
33%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,780,500 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w08w19w110w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x05e1eba1…6491
0x34b655…2a6f
4 touches
1 conflict
0x330a0e84…0d91
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4caf91f9…8ab5
0x34b655…2a6f
4 touches
1 conflict
0x4e66a473…9fe8
0x34b655…2a6f
4 touches
1 conflict
0x6d99ac64…0aa3
0x34b655…2a6f
4 touches
1 conflict
0x6febb84c…5b3b
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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 0x05e1eba1fd…456491
Audit this contract →
← previous block·next block →recent activity