← previous blocknext block →recent activity
Analyzing
Block #86,339,530
12 transactions · 11 stateful · 2026-07-08 04:51:25 UTC
Parallelism
58/100
Blocked
36%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,339,530 · 12 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w19w210w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x16a8cd0c…27bd
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0x5ffc25fa…b119
0x34b655…2a6f
4 touches
1 conflict
0x9fc1c44c…a7b3
0x34b655…2a6f
4 touches
1 conflict
0xb8228d38…3953
0x34b655…2a6f
4 touches
1 conflict
0x034f1f86…4e8d
0x34b655…2a6f
2 touches
0 conflicts
0x4bfdcd51…9b58
0x34b655…2a6f
2 touches
0 conflicts
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 0x16a8cd0cae…8827bd
Audit this contract →
← previous block·next block →recent activity