← previous blocknext block →recent activity
Analyzing
Block #85,875,037
15 transactions · 14 stateful · 2026-07-06 01:11:03 UTC
Parallelism
80/100
Blocked
21%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,875,037 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w012w013w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0xd8834cf3…0004
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xdd3a7a57…2fa6
0xd32edf…ff58
3 touches
1 conflict
0x21898044…a071
0x065c9d…c394
2 touches
0 conflicts
0x4ec6446c…3888
0x065c9d…c394
2 touches
0 conflicts
0xc3ecbd6f…46ed
0x065c9d…c394
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity