← previous blocknext block →recent activity
Analyzing
Block #86,621,436
15 transactions · 12 stateful · 2026-07-09 12:16:55 UTC
Parallelism
73/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,621,436 · 15 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
3w04w15w06w19w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e782d17…5318
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x5e782d17…5317
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xda8d6085…7b09
0x34b655…2a6f
5 touches
3 conflicts
0x5e2ea201…12de
0x34b655…2a6f
4 touches
1 conflict
0xbe67b007…b561
0x34b655…2a6f
4 touches
1 conflict
0x4984f7be…d515
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
3 conflicts on slot 0x5e782d178d…db5318
Audit this contract →
← previous block·next block →recent activity