← previous blocknext block →recent activity
Analyzing
Block #86,713,365
15 transactions · 13 stateful · 2026-07-09 22:31:56 UTC
Parallelism
80/100
Blocked
31%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,713,365 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w19w211w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e782d17…5318
0x34b655…2a6f
6 touches
3 conflicts
0x9ec0223e…8bea
0x34b655…2a6f
6 touches
3 conflicts
0x4984f7be…d515
0x34b655…2a6f
6 touches
3 conflicts
0x1a73b0f4…7126
0x34b655…2a6f
6 touches
3 conflicts
0x5e782d17…5317
0x34b655…2a6f
6 touches
3 conflicts
0xdbf50b38…ac8c
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x7d6b9af1…9a38
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