← previous blocknext block →recent activity
Analyzing
Block #86,852,350
31 transactions · 25 stateful · 2026-07-10 14:00:43 UTC
Parallelism
39/100
Blocked
76%
Avg conflicts / tx
3.23
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #86,852,350 · 31 txs across 19 waves · depth 19
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w49w510w611w713w823w926w1428w1629w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1928db9c…6ea9
0x34b655…2a6f
20 touches
45 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
18 touches
36 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
16 touches
28 conflicts
0x288bc578…318e
0x34b655…2a6f
16 touches
28 conflicts
0x7523ad90…2ba5
0x34b655…2a6f
16 touches
28 conflicts
0x9f40a209…1193
0x34b655…2a6f
16 touches
28 conflicts
0xc0b9bd73…7f1c
0x34b655…2a6f
16 touches
28 conflicts
0xc368d7fd…aaec
0x34b655…2a6f
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
45 conflicts on slot 0x1928db9c9b…476ea9
Audit this contract →
← previous block·next block →recent activity