← previous blocknext block →recent activity
Analyzing
Block #86,924,727
19 transactions · 18 stateful · 2026-07-10 22:04:42 UTC
Parallelism
58/100
Blocked
44%
Avg conflicts / tx
1.53
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,924,727 · 19 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
2w03w14w25w36w47w512w614w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
14 touches
21 conflicts
0x4a5df61e…a961
0x34b655…2a6f
12 touches
15 conflicts
0xfaef08b1…0696
0x34b655…2a6f
12 touches
15 conflicts
0xb0bc3bf8…e2b1
0x34b655…2a6f
12 touches
15 conflicts
0x7ee6007b…fd68
0x34b655…2a6f
10 touches
10 conflicts
0x855f0894…e5ac
0x34b655…2a6f
10 touches
10 conflicts
0xa0efa7bc…8b24
0x34b655…2a6f
10 touches
10 conflicts
0xaa48195d…ffee
0x34b655…2a6f
10 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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity