← previous blocknext block →recent activity
Analyzing
Block #85,537,546
10 transactions · 10 stateful · 2026-07-04 11:42:22 UTC
Parallelism
60/100
Blocked
30%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,537,546 · 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
2w03w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x517d35c7…f359
0x34b655…2a6f
6 touches
3 conflicts
0x10d9dbcb…9fdb
0x34b655…2a6f
4 touches
1 conflict
0x11431f9d…42c5
0x34b655…2a6f
4 touches
1 conflict
0x329f2f7d…dcff
0x34b655…2a6f
4 touches
1 conflict
0x3a4661c8…68ec
0x34b655…2a6f
4 touches
1 conflict
0x408d584a…8309
0x34b655…2a6f
4 touches
1 conflict
0x46887a39…f0a1
0x34b655…2a6f
4 touches
1 conflict
0x4eb98096…65c2
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 0x517d35c7d4…69f359
Audit this contract →
← previous block·next block →recent activity