← previous blocknext block →recent activity
Analyzing
Block #86,779,136
11 transactions · 9 stateful · 2026-07-10 05:51:22 UTC
Parallelism
64/100
Blocked
33%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,779,136 · 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
2w03w14w25w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x19ba76c3…6342
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xf5042875…9a93
0x34b655…2a6f
4 touches
1 conflict
0xb7b8bfda…efc0
0x34b655…2a6f
4 touches
1 conflict
0xc317001d…7351
0x34b655…2a6f
4 touches
1 conflict
0xd4a367b6…1456
0x34b655…2a6f
4 touches
1 conflict
0x4c623175…29e4
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
6 conflicts on slot 0x19ba76c35e…d56342
Audit this contract →
← previous block·next block →recent activity