← previous blocknext block →recent activity
Analyzing
Block #85,678,841
11 transactions · 9 stateful · 2026-07-05 03:23:09 UTC
Parallelism
73/100
Blocked
44%
Avg conflicts / tx
0.45
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,678,841 · 11 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
1w02w13w04w15w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xea9e7e38…819b
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xb68e226d…c054
0xa6afd3…d132
4 touches
1 conflict
0xca0f0668…caf3
0xa6afd3…d132
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
2 touches
0 conflicts
0xba5743c7…21c3
0x1b6862…e19c
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity