← previous blocknext block →recent activity

Analyzing

Block #85,107,285

20 transactions · 20 stateful · 2026-07-02 11:56:13 UTC

Parallelism

70/100

Blocked

45%

Avg conflicts / tx

1.05

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #85,107,285  ·  20 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0xfaef08b1…0696

0x34b655…2a6f

12 touches
15 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0x0720d2a9…57f6

0x34b655…2a6f

4 touches
1 conflict

0x0f12a71f…17a5

0x34b655…2a6f

4 touches
1 conflict

0x16b3a441…13db

0x34b655…2a6f

4 touches
1 conflict

0x61ed17e0…d6d9

0x34b655…2a6f

4 touches
1 conflict

0x664bf99e…0a8c

0x34b655…2a6f

4 touches
1 conflict

0x7b3da897…b268

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

15 conflicts on slot 0xfaef08b108…f90696

← previous block·next block →recent activity