← previous blocknext block →recent activity
Analyzing
Block #85,791,641
10 transactions · 7 stateful · 2026-07-05 15:55:34 UTC
Parallelism
60/100
Blocked
43%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,791,641 · 10 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
1w04w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38d0f220…01f4
0x34b655…2a6f
6 touches
3 conflicts
0x57b73d86…2fcb
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x14a71e9b…8870
0x34b655…2a6f
4 touches
1 conflict
0x97f73039…aa68
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2d
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2e
0x34b655…2a6f
4 touches
1 conflict
0x8595db3e…c610
0x34b655…2a6f
3 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 0x38d0f220b3…5301f4
Audit this contract →
← previous block·next block →recent activity