← previous blocknext block →recent activity
Analyzing
Block #86,804,359
16 transactions · 13 stateful · 2026-07-10 08:39:48 UTC
Parallelism
81/100
Blocked
23%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,804,359 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w09w111w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcbe18c62…3a5c
0x34b655…2a6f
4 touches
1 conflict
0xcbe18c62…3a5d
0x34b655…2a6f
4 touches
1 conflict
0xd8bc53a3…c2fe
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x65f04737…dc23
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x04814553…3017
0x34b655…2a6f
2 touches
0 conflicts
0x0cf9b588…7dbc
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xcbe18c620b…303a5c
Audit this contract →
← previous block·next block →recent activity