← previous blocknext block →recent activity
Analyzing
Block #86,847,966
26 transactions · 20 stateful · 2026-07-10 13:31:24 UTC
Parallelism
77/100
Blocked
55%
Avg conflicts / tx
0.92
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,847,966 · 26 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w17w08w19w010w114w015w216w317w222w423w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec7fe04a…3c56
0x34b655…2a6f
10 touches
10 conflicts
0x2760eac9…75e5
0xd32edf…ff58
7 touches
6 conflicts
0xe954af0e…b8f3
0x34b655…2a6f
6 touches
3 conflicts
0xa4f80979…4d71
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x08cc68a2…2a59
0x34b655…2a6f
4 touches
1 conflict
0x1c22c33c…36b6
0x34b655…2a6f
4 touches
1 conflict
0x434b7839…d546
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
10 conflicts on slot 0xec7fe04ad1…2d3c56
Audit this contract →
← previous block·next block →recent activity