← previous blocknext block →recent activity
Analyzing
Block #86,904,913
28 transactions · 28 stateful · 2026-07-10 19:52:16 UTC
Parallelism
75/100
Blocked
50%
Avg conflicts / tx
1.14
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,904,913 · 28 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
1w02w14w05w16w27w38w49w510w616w217w319w126w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
14 touches
21 conflicts
0x19b8ee99…c08a
0x34b655…2a6f
8 touches
6 conflicts
0x1cc39c91…f518
0x34b655…2a6f
8 touches
6 conflicts
0x472dd61b…64fe
0x34b655…2a6f
8 touches
6 conflicts
0x5fee1ba0…2520
0x34b655…2a6f
8 touches
6 conflicts
0x727fbce7…0c80
0x34b655…2a6f
8 touches
6 conflicts
0x7da56943…9753
0x34b655…2a6f
8 touches
6 conflicts
0xa0efa7bc…8b24
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
21 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity