← previous blocknext block →recent activity
Analyzing
Block #86,855,278
25 transactions · 22 stateful · 2026-07-10 14:20:20 UTC
Parallelism
80/100
Blocked
41%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,855,278 · 25 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
2w03w16w07w18w29w313w014w116w219w320w124w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x202c03eb…cf33
0xa6afd3…d132
8 touches
6 conflicts
0xdec5bfea…d17f
0xa6afd3…d132
8 touches
6 conflicts
0xc6ed530e…fa7d
0x34b655…2a6f
6 touches
3 conflicts
0x4f4bdabd…ffba
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xa07e7b13…7513
0x34b655…2a6f
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
6 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity