← previous blocknext block →recent activity
Analyzing
Block #86,686,831
16 transactions · 14 stateful · 2026-07-09 19:34:56 UTC
Parallelism
69/100
Blocked
36%
Avg conflicts / tx
0.38
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,686,831 · 16 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
2w03w16w17w213w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x511ecf07…8ed0
0x34b655…2a6f
6 touches
3 conflicts
0x02c4bb0f…f2c8
0x34b655…2a6f
4 touches
1 conflict
0x03fb27fd…0c06
0x34b655…2a6f
4 touches
1 conflict
0x0b202b66…0409
0x34b655…2a6f
4 touches
1 conflict
0x39423b28…1e57
0x34b655…2a6f
4 touches
1 conflict
0x3d51c4f1…652d
0x34b655…2a6f
4 touches
1 conflict
0x3e505a15…70f8
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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 0x511ecf073e…d98ed0
Audit this contract →
← previous block·next block →recent activity