← previous blocknext block →recent activity
Analyzing
Block #86,322,869
32 transactions · 28 stateful · 2026-07-08 03:00:11 UTC
Parallelism
88/100
Blocked
36%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,322,869 · 32 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
2w03w04w16w17w210w011w114w019w220w322w023w124w025w228w229w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x65903ef9…2567
0x34b655…2a6f
8 touches
6 conflicts
0x96dd83e6…a507
0x34b655…2a6f
6 touches
3 conflicts
0x0fac8ebf…9e6c
0x34b655…2a6f
4 touches
1 conflict
0x559447b0…eb51
0x34b655…2a6f
4 touches
1 conflict
0x89b68259…26dc
0x34b655…2a6f
4 touches
1 conflict
0xb0088d1b…34fe
0x34b655…2a6f
4 touches
1 conflict
0xd8834cf3…0004
0x34b655…2a6f
4 touches
1 conflict
0xd99b3b64…1c95
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 0x65903ef9a0…7d2567
Audit this contract →
← previous block·next block →recent activity