← previous blocknext block →recent activity
Analyzing
Block #86,664,126
18 transactions · 16 stateful · 2026-07-09 17:03:21 UTC
Parallelism
67/100
Blocked
56%
Avg conflicts / tx
0.78
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,664,126 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w07w18w210w311w412w314w515w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5a9274d…78d7
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x8a35acfb…d1a6
0xb1dbf0…c0d3
6 touches
3 conflicts
0xa29182a1…c12c
0x34b655…2a6f
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
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
3 conflicts on slot 0xe5a9274d87…0678d7
Audit this contract →
← previous block·next block →recent activity