← previous blocknext block →recent activity

Analyzing

Block #85,158,038

24 transactions · 20 stateful · 2026-07-02 17:35:05 UTC

Parallelism

79/100

Blocked

40%

Avg conflicts / tx

0.63

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #85,158,038  ·  24 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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xfaef08b1…0696

0x34b655…2a6f

6 touches
3 conflicts

0x16dd4eb3…446c

0x34b655…2a6f

4 touches
1 conflict

0x170e4e4c…2b90

0x34b655…2a6f

4 touches
1 conflict

0x274b85f7…c526

0x34b655…2a6f

4 touches
1 conflict

0x352a9f83…5587

0x34b655…2a6f

4 touches
1 conflict

0x40b5f387…a164

0x34b655…2a6f

4 touches
1 conflict

0x4b93c963…e48b

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

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity