← previous blocknext block →recent activity
Analyzing
Block #86,836,442
27 transactions · 23 stateful · 2026-07-10 12:14:27 UTC
Parallelism
78/100
Blocked
35%
Avg conflicts / tx
0.44
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,836,442 · 27 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w08w110w014w015w116w117w224w325w426w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8d888c90…5479
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x64a785e4…0110
0x34b655…2a6f
4 touches
1 conflict
0x6e90b9b1…dca8
0x34b655…2a6f
4 touches
1 conflict
0x881fc98e…23d2
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 0x8d888c9003…aa5479
Audit this contract →
← previous block·next block →recent activity