← previous blocknext block →recent activity

Analyzing

Block #85,143,997

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

Parallelism

82/100

Blocked

13%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #85,143,997  ·  17 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xb04d17a0…10e8

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xfefb0189…f726

0x34b655…2a6f

4 touches
1 conflict

0x1bb0e721…db0c

0x34b655…2a6f

4 touches
1 conflict

0x4f71be9f…50b7

0x34b655…2a6f

4 touches
1 conflict

0x67dfc52c…cb5f

0x34b655…2a6f

4 touches
1 conflict

0x771754b8…1e8d

0x34b655…2a6f

4 touches
1 conflict

0xa2cc62d4…69f6

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

3 conflicts on slot 0xb04d17a0fe…4810e8

← previous block·next block →recent activity