← previous blocknext block →recent activity

Analyzing

Block #85,159,845

20 transactions · 19 stateful · 2026-07-02 17:47:07 UTC

Parallelism

70/100

Blocked

37%

Avg conflicts / tx

0.7

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #85,159,845  ·  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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x326a02b5…8dad

0x34b655…2a6f

6 touches
3 conflicts

0xd99b3b64…1c95

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0x93d4b4e9…5daa

0x851145…3f07

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x2886e2bc…6ab8

0x065c9d…c394

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