← previous blocknext block →recent activity
Analyzing
Block #85,670,103
10 transactions · 10 stateful · 2026-07-05 02:25:01 UTC
Parallelism
60/100
Blocked
30%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,670,103 · 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
2w07w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6cdad76f…2bed
0x34b655…2a6f
6 touches
3 conflicts
0xe6c82b1e…86cb
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
6 touches
3 conflicts
0xfdde6236…b2a5
0x34b655…2a6f
6 touches
3 conflicts
0x4dd3efe6…f040
0x34b655…2a6f
4 touches
1 conflict
0x5235e55b…adf2
0x34b655…2a6f
4 touches
1 conflict
0x548145a9…cfce
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 0x6cdad76fd1…3a2bed
Audit this contract →
← previous block·next block →recent activity