← previous blocknext block →recent activity
Analyzing
Block #86,513,983
28 transactions · 23 stateful · 2026-07-09 00:17:00 UTC
Parallelism
71/100
Blocked
48%
Avg conflicts / tx
1.36
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,513,983 · 28 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w26w07w19w010w213w314w415w516w617w721w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
14 touches
21 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
12 touches
15 conflicts
0x63c900f4…2600
0x34b655…2a6f
10 touches
10 conflicts
0x3483ab79…8ed3
0x34b655…2a6f
10 touches
10 conflicts
0x7c0bdc54…9dde
0x34b655…2a6f
10 touches
10 conflicts
0xa1144aa9…7f67
0x34b655…2a6f
10 touches
10 conflicts
0x922c7ebd…6600
0xc8689a…ee79
10 touches
10 conflicts
0x9138a113…0d5f
0x34b655…2a6f
9 touches
10 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
21 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity