← previous blocknext block →recent activity
Analyzing
Block #86,613,712
30 transactions · 25 stateful · 2026-07-09 11:25:21 UTC
Parallelism
83/100
Blocked
40%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,613,712 · 30 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
1w04w05w18w09w110w011w215w016w317w420w121w224w126w128w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8b501dcf…1040
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x671703d0…94b1
0x34b655…2a6f
4 touches
1 conflict
0x8eb0ac6b…a73a
0x34b655…2a6f
4 touches
1 conflict
0xa013ecc1…7c8f
0x34b655…2a6f
4 touches
1 conflict
0xa7013be2…c0a8
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 0x8b501dcf17…471040
Audit this contract →
← previous block·next block →recent activity