← previous blocknext block →recent activity
Analyzing
Block #86,512,692
11 transactions · 8 stateful · 2026-07-09 00:08:22 UTC
Parallelism
64/100
Blocked
38%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,512,692 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e6bea03…1835
0x34b655…2a6f
6 touches
3 conflicts
0xf195ad96…e0c3
0x34b655…2a6f
4 touches
1 conflict
0x88e771e8…7d4a
0x34b655…2a6f
4 touches
1 conflict
0x89999c15…fdac
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0xa7ec6b56…396f
0x34b655…2a6f
4 touches
1 conflict
0xac0b4a08…faae
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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 0x7e6bea036d…471835
Audit this contract →
← previous block·next block →recent activity