← previous blocknext block →recent activity
Analyzing
Block #86,711,416
8 transactions · 5 stateful · 2026-07-09 22:18:54 UTC
Parallelism
75/100
Blocked
20%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,711,416 · 8 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x8a35acfb…d1a7
0xb1dbf0…c0d3
4 touches
1 conflict
0x8a35acfb…d1a8
0xb1dbf0…c0d3
4 touches
1 conflict
0x6fdc73d3…9853
0xb1dbf0…c0d3
3 touches
1 conflict
0xd040d680…4b05
0xb1dbf0…c0d3
3 touches
1 conflict
0x9c540cb6…ea0c
0x34b655…2a6f
2 touches
0 conflicts
0x9f385104…728a
0x34b655…2a6f
2 touches
0 conflicts
0xaa16fd7b…ec3c
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 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity