← previous blocknext block →recent activity
Analyzing
Block #86,484,682
10 transactions · 7 stateful · 2026-07-08 21:01:32 UTC
Parallelism
60/100
Blocked
43%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,484,682 · 10 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
1w02w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7ee6007b…fd68
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x08de772c…8e84
0x2a68ba…90c5
2 touches
0 conflicts
0xaeb5864c…7679
0x2a68ba…90c5
2 touches
0 conflicts
0x0e9a70ab…e67c
0x34b655…2a6f
2 touches
0 conflicts
0x3d4584df…ffed
0x34b655…2a6f
2 touches
0 conflicts
0x49f6ddba…b7de
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
3 conflicts on slot 0x7ee6007b44…92fd68
Audit this contract →
← previous block·next block →recent activity