← previous blocknext block →recent activity
Analyzing
Block #86,768,280
18 transactions · 17 stateful · 2026-07-10 04:38:56 UTC
Parallelism
78/100
Blocked
24%
Avg conflicts / tx
0.28
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,768,280 · 18 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
5w06w08w112w116w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0c53719e…0366
0x34b655…2a6f
4 touches
1 conflict
0x1928db9c…6ea9
0x34b655…2a6f
4 touches
1 conflict
0x1a61d83a…5f35
0x34b655…2a6f
4 touches
1 conflict
0x3a6290da…e683
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x686e8614…1a77
0x34b655…2a6f
4 touches
1 conflict
0x76c4467d…ce28
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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
1 conflict on slot 0x0c53719e11…2e0366
Audit this contract →
← previous block·next block →recent activity