← previous blocknext block →recent activity
Analyzing
Block #85,897,653
32 transactions · 23 stateful · 2026-07-06 03:41:44 UTC
Parallelism
88/100
Blocked
17%
Avg conflicts / tx
0.16
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,897,653 · 32 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
1w018w122w028w129w230w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x5856e713…7929
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x59dccbd8…2bf6
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x78b6c319…bac0
0x3c2269…cf62
2 touches
0 conflicts
0xa3681dc1…7a3d
0x3c2269…cf62
2 touches
0 conflicts
0xb6226823…c2e1
0x3c2269…cf62
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