← previous blocknext block →recent activity

Analyzing

Block #86,258,775

19 transactions · 17 stateful · 2026-07-07 19:52:17 UTC

Parallelism

79/100

Blocked

41%

Avg conflicts / tx

0.53

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,258,775  ·  19 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x0efc210e…70ab

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x3b9bb58c…e73a

0x34b655…2a6f

6 touches
3 conflicts

0x077d58c3…8ed7

0x34b655…2a6f

4 touches
1 conflict

0x07d40a77…7a50

0x34b655…2a6f

4 touches
1 conflict

0x0c423b46…8777

0x34b655…2a6f

4 touches
1 conflict

0x0db8e93a…7dd1

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