← previous blocknext block →recent activity
Analyzing
Block #86,215,183
20 transactions · 18 stateful · 2026-07-07 15:01:02 UTC
Parallelism
75/100
Blocked
50%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,215,183 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w17w28w39w314w015w116w217w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x0efc210e…70ab
0x34b655…2a6f
4 touches
1 conflict
0x202c03eb…cf33
0xa6afd3…d132
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x4d3e58e0…a2d7
0x34b655…2a6f
4 touches
1 conflict
0xa62f5f3e…a902
0xa6afd3…d132
4 touches
1 conflict
0xdec5bfea…d17f
0xa6afd3…d132
4 touches
1 conflict
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity