← previous blocknext block →recent activity

Analyzing

Block #85,190,325

17 transactions · 16 stateful · 2026-07-02 21:10:01 UTC

Parallelism

76/100

Blocked

38%

Avg conflicts / tx

0.82

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #85,190,325  ·  17 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…003d

0x40c49f…2af0

4 touches
1 conflict

0x7506443a…4820

0x34b655…2a6f

4 touches
1 conflict

0x98834cc0…6c23

0x34b655…2a6f

4 touches
1 conflict

0xcc6e2e88…6569

0x34b655…2a6f

4 touches
1 conflict

0xd19c9d38…b459

0x34b655…2a6f

4 touches
1 conflict

0xd63e616b…a07d

0x34b655…2a6f

4 touches
1 conflict

0xd8834cf3…0004

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity