← previous blocknext block →recent activity
Analyzing
Block #86,787,465
28 transactions · 22 stateful · 2026-07-10 06:46:58 UTC
Parallelism
86/100
Blocked
45%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,787,465 · 28 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
1w02w04w05w18w19w110w112w013w114w216w219w020w221w127w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe100a7a6…cf18
0x34b655…2a6f
8 touches
6 conflicts
0xb6ed530c…d450
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x78a42428…b3f1
0x065c9d…c394
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xfadc118d…5d64
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0xa0c37dda…60a3
0x065c9d…c394
5 touches
3 conflicts
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 0xe100a7a6d9…c6cf18
Audit this contract →
← previous block·next block →recent activity