← previous blocknext block →recent activity
Analyzing
Block #85,251,444
14 transactions · 13 stateful · 2026-07-03 03:57:12 UTC
Parallelism
64/100
Blocked
31%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,251,444 · 14 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
2w03w04w05w111w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x27f2c756…0ffc
0x34b655…2a6f
6 touches
3 conflicts
0xcdc1731c…b91a
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x315e07b8…9823
0x34b655…2a6f
4 touches
1 conflict
0x9cf2d0bf…8d46
0x34b655…2a6f
4 touches
1 conflict
0x6680509c…3b83
0x34b655…2a6f
2 touches
0 conflicts
0x8cc510b5…9fa8
0x34b655…2a6f
2 touches
0 conflicts
0xb2fa7755…4c09
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 0x27f2c75698…900ffc
Audit this contract →
← previous block·next block →recent activity