← previous blocknext block →recent activity
Analyzing
Block #85,539,325
10 transactions · 10 stateful · 2026-07-04 11:54:14 UTC
Parallelism
80/100
Blocked
30%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,539,325 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w07w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbfca3cd0…5023
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x2d94ecd9…43db
0x34b655…2a6f
4 touches
1 conflict
0x02750307…5f2e
0x065c9d…c394
2 touches
0 conflicts
0x13064224…d51a
0x065c9d…c394
2 touches
0 conflicts
0x162b0967…1d06
0x065c9d…c394
2 touches
0 conflicts
0x7f00c3f8…9a4c
0x065c9d…c394
2 touches
0 conflicts
0x9a8f8d9c…67ec
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
1 conflict on slot 0xbfca3cd067…cd5023
Audit this contract →
← previous block·next block →recent activity