← previous blocknext block →recent activity
Analyzing
Block #86,835,538
15 transactions · 12 stateful · 2026-07-10 12:08:25 UTC
Parallelism
73/100
Blocked
25%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,835,538 · 15 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
5w06w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8f60ec18…c267
0x34b655…2a6f
6 touches
3 conflicts
0xf83b23f9…5a2f
0x34b655…2a6f
4 touches
1 conflict
0x042f0919…8779
0x34b655…2a6f
4 touches
1 conflict
0x2efd1517…0726
0x34b655…2a6f
4 touches
1 conflict
0x488ec42b…8985
0x34b655…2a6f
4 touches
1 conflict
0x4fa2386a…7e33
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xf83b23f9…5a2e
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 0x8f60ec18f1…3ac267
Audit this contract →
← previous block·next block →recent activity