← previous blocknext block →recent activity

Analyzing

Block #86,152,373

31 transactions · 25 stateful · 2026-07-07 08:01:41 UTC

Parallelism

84/100

Blocked

28%

Avg conflicts / tx

0.35

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,152,373  ·  31 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x94dabb65…43a3

0x34b655…2a6f

8 touches
6 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x09898c8d…125d

0x34b655…2a6f

4 touches
1 conflict

0x157dbfb2…4089

0x34b655…2a6f

4 touches
1 conflict

0x3a6290da…e683

0x34b655…2a6f

4 touches
1 conflict

0x456f4453…91f0

0x34b655…2a6f

4 touches
1 conflict

0x584cbe31…38e5

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

6 conflicts on slot 0x94dabb6529…f943a3

← previous block·next block →recent activity