← previous blocknext block →recent activity
Analyzing
Block #86,905,271
24 transactions · 20 stateful · 2026-07-10 19:54:40 UTC
Parallelism
71/100
Blocked
40%
Avg conflicts / tx
1.17
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,905,271 · 24 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
4w05w16w27w39w010w415w516w518w623w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
12 touches
15 conflicts
0x70b87e4d…65d5
0x34b655…2a6f
12 touches
15 conflicts
0x7a88ba8e…1b0d
0x34b655…2a6f
10 touches
10 conflicts
0xa3e06ffb…6c2b
0x34b655…2a6f
10 touches
10 conflicts
0x2505abf0…6bac
0x34b655…2a6f
8 touches
6 conflicts
0x50309e43…fe33
0x34b655…2a6f
8 touches
6 conflicts
0x5fee1ba0…2520
0x34b655…2a6f
8 touches
6 conflicts
0x727fbce7…0c80
0x34b655…2a6f
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
15 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity