← previous blocknext block →recent activity
Analyzing
Block #86,682,158
30 transactions · 26 stateful · 2026-07-09 19:03:44 UTC
Parallelism
77/100
Blocked
50%
Avg conflicts / tx
1.13
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,682,158 · 30 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w17w210w311w412w515w016w117w121w222w323w629w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea02471d…1542
0x34b655…2a6f
10 touches
10 conflicts
0xe211b485…55a9
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0018
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0028
0x1b6862…e19c
8 touches
6 conflicts
0xba5743c7…21bf
0x1b6862…e19c
8 touches
6 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
10 conflicts on slot 0xea02471df2…601542
Audit this contract →
← previous block·next block →recent activity