← previous blocknext block →recent activity

Analyzing

Block #85,012,093

23 transactions · 15 stateful · 2026-07-02 01:19:26 UTC

Parallelism

70/100

Blocked

53%

Avg conflicts / tx

1

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #85,012,093  ·  23 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

14 touches
21 conflicts

0x99479bc5…3a88

0x34b655…2a6f

8 touches
6 conflicts

0x18f5386c…12aa

0x34b655…2a6f

6 touches
3 conflicts

0x53cccb07…d7f0

0x34b655…2a6f

6 touches
3 conflicts

0xec63e4f6…4778

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

4 touches
1 conflict

0x424eca3b…f2ab

0xa6afd3…d132

4 touches
1 conflict

0xdc120748…ff36

0xa6afd3…d132

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

21 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity