← previous blocknext block →recent activity

Analyzing

Block #86,950,378

23 transactions · 20 stateful · 2026-07-11 00:56:02 UTC

Parallelism

83/100

Blocked

35%

Avg conflicts / tx

0.43

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,950,378  ·  23 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

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xfaef08b1…0696

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x0733be30…112f

0x34b655…2a6f

6 touches
3 conflicts

0x76f784b3…7e00

0x34b655…2a6f

4 touches
1 conflict

0x9138a113…0d5f

0x34b655…2a6f

4 touches
1 conflict

0xa1cdfee6…a957

0x34b655…2a6f

4 touches
1 conflict

0xa3e06ffb…6c2b

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 0x482471adbb…39122f

← previous block·next block →recent activity