← previous blocknext block →recent activity
Analyzing
Block #86,103,269
13 transactions · 11 stateful · 2026-07-07 02:33:50 UTC
Parallelism
85/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,103,269 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe4af4c87…9964
0x34b655…2a6f
4 touches
1 conflict
0xe5eb3c33…0e3a
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x26b0fa60…c1cc
0x34b655…2a6f
2 touches
0 conflicts
0x2ed98d3b…78ef
0x34b655…2a6f
2 touches
0 conflicts
0x30fa662a…06e0
0x34b655…2a6f
2 touches
0 conflicts
0x392bf56c…4078
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xe4af4c87c3…c59964
Audit this contract →
← previous block·next block →recent activity