← previous blocknext block →recent activity
Analyzing
Block #85,597,007
12 transactions · 11 stateful · 2026-07-04 18:18:27 UTC
Parallelism
75/100
Blocked
27%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,597,007 · 12 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
1w07w08w19w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5fe7e126…6dd2
0x34b655…2a6f
6 touches
3 conflicts
0xadadad23…f057
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x4044a18a…8e8c
0x34b655…2a6f
4 touches
1 conflict
0x9ddbc6a8…45f1
0x34b655…2a6f
4 touches
1 conflict
0x89649720…5a3d
0x065c9d…c394
3 touches
1 conflict
0x00000000…0005
0x5afd3e…7620
2 touches
0 conflicts
0x0dccec4e…3636
0x5afd3e…7620
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 0x5fe7e1267e…896dd2
Audit this contract →
← previous block·next block →recent activity