← previous blocknext block →recent activity
Analyzing
Block #86,814,748
10 transactions · 10 stateful · 2026-07-10 09:49:13 UTC
Parallelism
50/100
Blocked
40%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,814,748 · 10 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w17w28w39w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2264392…d5f4
0x34b655…2a6f
8 touches
6 conflicts
0xf5db3b52…5e79
0x34b655…2a6f
6 touches
3 conflicts
0x140eb1ca…bc07
0x34b655…2a6f
6 touches
3 conflicts
0x25191452…d2ed
0x34b655…2a6f
6 touches
3 conflicts
0x40287836…2dff
0x34b655…2a6f
6 touches
3 conflicts
0x59b0a8da…0928
0x34b655…2a6f
6 touches
3 conflicts
0x8d888c90…5479
0x34b655…2a6f
6 touches
3 conflicts
0xc02ac297…5111
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0xe2264392ec…c0d5f4
Audit this contract →
← previous block·next block →recent activity