← previous blocknext block →recent activity

Analyzing

Block #85,140,421

21 transactions · 19 stateful · 2026-07-02 15:37:44 UTC

Parallelism

62/100

Blocked

47%

Avg conflicts / tx

0.76

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #85,140,421  ·  21 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xb04d17a0…10e8

0x34b655…2a6f

6 touches
3 conflicts

0xfaef08b1…0696

0x34b655…2a6f

6 touches
3 conflicts

0x08cc68a2…2a59

0x34b655…2a6f

4 touches
1 conflict

0x0939bc15…c5e8

0x34b655…2a6f

4 touches
1 conflict

0x264f7d7d…8444

0x34b655…2a6f

4 touches
1 conflict

0x53b4ef2b…8a05

0x34b655…2a6f

4 touches
1 conflict

0x587911c7…9e01

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