← previous blocknext block →recent activity

Analyzing

Block #86,693,948

19 transactions · 19 stateful · 2026-07-09 20:22:22 UTC

Parallelism

84/100

Blocked

32%

Avg conflicts / tx

0.47

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,693,948  ·  19 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xcc3f7ee8…7924

0x34b655…2a6f

6 touches
3 conflicts

0x74888025…a5b8

0x34b655…2a6f

6 touches
3 conflicts

0x42041fec…bd86

0x754704…b603

6 touches
3 conflicts

0x256abea8…f282

0x34b655…2a6f

4 touches
1 conflict

0x2d7ea048…d78e

0x34b655…2a6f

4 touches
1 conflict

0x745a7fd6…5fea

0x34b655…2a6f

4 touches
1 conflict

0x03fb27fd…0c06

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity