← previous blocknext block →recent activity
Analyzing
Block #86,776,269
16 transactions · 14 stateful · 2026-07-10 05:32:16 UTC
Parallelism
81/100
Blocked
36%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,776,269 · 16 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
1w02w13w04w17w18w29w010w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1efd237f…6d36
0x34b655…2a6f
6 touches
3 conflicts
0x8a35acfb…d1a8
0xb1dbf0…c0d3
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4984f7be…d515
0x34b655…2a6f
4 touches
1 conflict
0x7d16a9bc…25db
0x34b655…2a6f
4 touches
1 conflict
0x89999c15…fdac
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 0x1efd237f80…6f6d36
Audit this contract →
← previous block·next block →recent activity