← previous blocknext block →recent activity

Analyzing

Block #86,272,052

25 transactions · 20 stateful · 2026-07-07 21:20:47 UTC

Parallelism

72/100

Blocked

45%

Avg conflicts / tx

0.84

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #86,272,052  ·  25 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

10 touches
10 conflicts

0x96dd83e6…a507

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0002

0x04fdea…47d7

6 touches
3 conflicts

0x2267f8c4…a571

0x34b655…2a6f

6 touches
3 conflicts

0x69ce640b…884a

0x34b655…2a6f

6 touches
3 conflicts

0xb54facbb…1914

0x34b655…2a6f

6 touches
3 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

6 touches
3 conflicts

0x2697123c…8526

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

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity