← previous blocknext block →recent activity
Analyzing
Block #86,490,592
26 transactions · 21 stateful · 2026-07-08 21:41:01 UTC
Parallelism
81/100
Blocked
48%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,490,592 · 26 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
3w06w17w08w19w210w011w112w217w122w123w224w325w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x1cd9eb1d…f26f
0x34b655…2a6f
4 touches
1 conflict
0x2bf5914f…c75d
0x34b655…2a6f
4 touches
1 conflict
0x59dccbd8…2bf6
0x34b655…2a6f
4 touches
1 conflict
0x6fc361a0…11fc
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity