← previous blocknext block →recent activity
Analyzing
Block #86,917,101
21 transactions · 20 stateful · 2026-07-10 21:13:40 UTC
Parallelism
67/100
Blocked
60%
Avg conflicts / tx
1.48
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,917,101 · 21 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
1w02w13w24w05w16w27w38w49w510w620w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaa48195d…ffee
0x34b655…2a6f
14 touches
21 conflicts
0x04105a34…6eea
0x34b655…2a6f
14 touches
21 conflicts
0xe727ab72…768b
0x34b655…2a6f
14 touches
21 conflicts
0x74888025…a5b8
0x34b655…2a6f
14 touches
21 conflicts
0x922c7ebd…6600
0xc8689a…ee79
14 touches
21 conflicts
0x7ee6007b…fd68
0x34b655…2a6f
14 touches
21 conflicts
0xa0efa7bc…8b24
0x34b655…2a6f
14 touches
21 conflicts
0xfaef08b1…0696
0x34b655…2a6f
14 touches
21 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 0xaa48195d9c…daffee
Audit this contract →
← previous block·next block →recent activity