← previous blocknext block →recent activity

Analyzing

Block #86,679,693

20 transactions · 17 stateful · 2026-07-09 18:47:15 UTC

Parallelism

85/100

Blocked

41%

Avg conflicts / tx

0.5

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,679,693  ·  20 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

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0x059b51d7…19ff

0x34b655…2a6f

4 touches
1 conflict

0x1cdfe548…d3aa

0x34b655…2a6f

4 touches
1 conflict

0x30ae635d…5e67

0x34b655…2a6f

4 touches
1 conflict

0x328ddce5…1eb5

0x34b655…2a6f

4 touches
1 conflict

0x61631446…70ac

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

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