← previous blocknext block →recent activity
Analyzing
Block #85,108,324
28 transactions · 24 stateful · 2026-07-02 12:03:09 UTC
Parallelism
82/100
Blocked
42%
Avg conflicts / tx
0.68
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,108,324 · 28 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w16w27w39w010w111w212w317w320w422w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0xa0efa7bc…8b24
0x34b655…2a6f
6 touches
3 conflicts
0xaa48195d…ffee
0x34b655…2a6f
6 touches
3 conflicts
0x922c7ebd…6600
0xc8689a…ee79
6 touches
3 conflicts
0xc546686b…0e5e
0x34b655…2a6f
6 touches
3 conflicts
0xc5a0d88a…3aad
0x34b655…2a6f
6 touches
3 conflicts
0xcd4f4e08…35da
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity