← previous blocknext block →recent activity
Analyzing
Block #86,566,542
16 transactions · 11 stateful · 2026-07-09 06:09:03 UTC
Parallelism
81/100
Blocked
36%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,566,542 · 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
1w03w07w18w09w113w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xef5959a3…2a2f
0x34b655…2a6f
4 touches
1 conflict
0x56b5f5c0…a3ad
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x1299b030…e115
0x34b655…2a6f
2 touches
0 conflicts
0x1b374c44…96d9
0x34b655…2a6f
2 touches
0 conflicts
0x1e48811e…2e39
0x34b655…2a6f
2 touches
0 conflicts
0x51a9fa57…1dff
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 0xef5959a35a…d32a2f
Audit this contract →
← previous block·next block →recent activity