← previous blocknext block →recent activity
Analyzing
Block #86,847,729
19 transactions · 14 stateful · 2026-07-10 13:29:49 UTC
Parallelism
79/100
Blocked
43%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,847,729 · 19 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
1w02w13w111w012w113w114w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f42e42b…5717
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4ab
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xdcf93b63…ae96
0x34b655…2a6f
6 touches
3 conflicts
0x64800813…db9f
0x34b655…2a6f
4 touches
1 conflict
0x64852187…6caf
0x34b655…2a6f
4 touches
1 conflict
0x64852187…6cb0
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 0x6f42e42b3c…425717
Audit this contract →
← previous block·next block →recent activity