← previous blocknext block →recent activity
Analyzing
Block #86,924,538
33 transactions · 32 stateful · 2026-07-10 22:03:26 UTC
Parallelism
39/100
Blocked
69%
Avg conflicts / tx
5.36
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #86,924,538 · 33 txs across 20 waves · depth 20
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
wave w19
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w49w510w611w712w813w914w1015w1116w1217w1320w1328w1630w18
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x56b5f5c0…a3ad
0x34b655…2a6f
30 touches
105 conflicts
0xfaef08b1…0696
0x34b655…2a6f
28 touches
91 conflicts
0x041ecdd0…6228
0x34b655…2a6f
26 touches
78 conflicts
0xfd0f3e42…ecda
0x34b655…2a6f
26 touches
78 conflicts
0x17c3727d…cb0e
0x34b655…2a6f
26 touches
78 conflicts
0x3a996b35…bc8f
0x34b655…2a6f
26 touches
78 conflicts
0x5a9f6998…bc19
0x34b655…2a6f
26 touches
78 conflicts
0xe8377f79…5f5e
0x34b655…2a6f
26 touches
78 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
105 conflicts on slot 0x56b5f5c03e…07a3ad
Audit this contract →
← previous block·next block →recent activity