← previous blocknext block →recent activity
Analyzing
Block #86,614,675
24 transactions · 20 stateful · 2026-07-09 11:31:47 UTC
Parallelism
83/100
Blocked
40%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,614,675 · 24 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
1w02w14w05w18w210w211w312w316w017w121w023w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa29182a1…c12c
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x2d94ecd9…43db
0x34b655…2a6f
4 touches
1 conflict
0x30ae635d…5e67
0x34b655…2a6f
4 touches
1 conflict
0x3baddc3d…5d6d
0x34b655…2a6f
4 touches
1 conflict
0x3d715b82…3047
0x34b655…2a6f
4 touches
1 conflict
0x4ec9ff52…e6f7
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 0xa29182a19c…86c12c
Audit this contract →
← previous block·next block →recent activity