← previous blocknext block →recent activity
Analyzing
Block #86,445,366
29 transactions · 25 stateful · 2026-07-08 16:38:26 UTC
Parallelism
86/100
Blocked
28%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,445,366 · 29 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w112w213w318w220w022w226w027w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x071e17d4…fd91
0x34b655…2a6f
4 touches
1 conflict
0x1863f229…e5f4
0x34b655…2a6f
4 touches
1 conflict
0x199698ab…5768
0x34b655…2a6f
4 touches
1 conflict
0x37421b44…45b5
0x34b655…2a6f
4 touches
1 conflict
0x4a27be4f…c51a
0x34b655…2a6f
4 touches
1 conflict
0x5e2ea201…12de
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