← previous blocknext block →recent activity

Analyzing

Block #85,107,630

18 transactions · 16 stateful · 2026-07-02 11:58:31 UTC

Parallelism

89/100

Blocked

13%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #85,107,630  ·  18 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xf026b487…668c

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0002

0x04fdea…47d7

4 touches
1 conflict

0x644919d7…9727

0x34b655…2a6f

4 touches
1 conflict

0x98fc5672…13c7

0x34b655…2a6f

4 touches
1 conflict

0xaa99c369…263d

0x34b655…2a6f

4 touches
1 conflict

0xc00597a5…d2bf

0x34b655…2a6f

4 touches
1 conflict

0xc0b9bd73…7f1c

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

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

1 conflict on slot 0xf026b487e0…ea668c

← previous block·next block →recent activity