← previous blocknext block →recent activity
Analyzing
Block #86,503,658
27 transactions · 23 stateful · 2026-07-08 23:08:09 UTC
Parallelism
89/100
Blocked
39%
Avg conflicts / tx
0.41
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,503,658 · 27 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
1w02w16w08w110w011w114w015w117w119w120w224w025w126w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x9a291a56…9a9c
0x34b655…2a6f
6 touches
3 conflicts
0xdf6fce37…9b58
0x34b655…2a6f
6 touches
3 conflicts
0xa55cdf2a…1c64
0x34b655…2a6f
4 touches
1 conflict
0xc0eb79d1…29a4
0x34b655…2a6f
4 touches
1 conflict
0xc16a09bc…b756
0x34b655…2a6f
4 touches
1 conflict
0xdad46343…1eb8
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
3 conflicts on slot 0x8bf661cb38…d4bcd2
Audit this contract →
← previous block·next block →recent activity