← previous blocknext block →recent activity
Analyzing
Block #86,816,258
23 transactions · 22 stateful · 2026-07-10 09:59:19 UTC
Parallelism
83/100
Blocked
32%
Avg conflicts / tx
0.35
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,816,258 · 23 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
1w05w06w18w011w012w013w118w119w120w121w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xed4a0d72…065f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0xa4f80979…4d71
0x065c9d…c394
4 touches
1 conflict
0xd35bb5ac…3586
0x065c9d…c394
4 touches
1 conflict
0xdf75b946…aef9
0x34b655…2a6f
4 touches
1 conflict
0xdf75b946…aefa
0x34b655…2a6f
4 touches
1 conflict
0x3ad1a07a…9591
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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
1 conflict on slot 0xed4a0d72e2…41065f
Audit this contract →
← previous block·next block →recent activity