← previous blocknext block →recent activity
Analyzing
Block #86,733,080
21 transactions · 18 stateful · 2026-07-10 00:43:42 UTC
Parallelism
81/100
Blocked
22%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,733,080 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
8w010w011w115w216w319w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xa08f40b2…9a93
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0xff196840…a453
0x34b655…2a6f
6 touches
3 conflicts
0xe718f3c7…c376
0x34b655…2a6f
6 touches
3 conflicts
0x2b5101ac…090b
0x34b655…2a6f
4 touches
1 conflict
0x4e10ffaa…5365
0x34b655…2a6f
4 touches
1 conflict
0x00958d6e…1d09
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
6 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity