← previous blocknext block →recent activity
Analyzing
Block #86,511,625
27 transactions · 24 stateful · 2026-07-09 00:01:15 UTC
Parallelism
85/100
Blocked
38%
Avg conflicts / tx
0.59
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,511,625 · 27 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
1w03w04w15w26w311w012w113w214w315w117w225w026w1
- 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
8 touches
6 conflicts
0xb43dc900…22f2
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x4572c9a0…5cf9
0x34b655…2a6f
4 touches
1 conflict
0x727fbce7…0c80
0x34b655…2a6f
4 touches
1 conflict
0x97785d36…2ac5
0x34b655…2a6f
4 touches
1 conflict
0xa7013be2…c0a8
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