← previous blocknext block →recent activity
Analyzing
Block #86,850,534
35 transactions · 32 stateful · 2026-07-10 13:48:35 UTC
Parallelism
71/100
Blocked
59%
Avg conflicts / tx
2.23
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #86,850,534 · 35 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w49w510w611w712w816w220w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
18 touches
36 conflicts
0x00000000…0002
0x019883…2a9a
16 touches
28 conflicts
0x00000000…0003
0x019883…2a9a
16 touches
28 conflicts
0x44ad89ba…cf83
0x0cc9b2…7777
16 touches
28 conflicts
0x99a3a7c1…1e2b
0x0cc9b2…7777
16 touches
28 conflicts
0x00000000…0000
0x019883…2a9a
16 touches
28 conflicts
0x9966da31…0d0f
0x34b655…2a6f
16 touches
28 conflicts
0xa10c86f8…4b74
0x3bd359…433a
16 touches
28 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
36 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity