← previous blocknext block →recent activity

Analyzing

Block #86,736,164

15 transactions · 11 stateful · 2026-07-10 01:04:18 UTC

Parallelism

80/100

Blocked

36%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,736,164  ·  15 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

0x0d2de0f6…e6c6

0x34b655…2a6f

6 touches
3 conflicts

0xe8e4c015…5718

0x34b655…2a6f

4 touches
1 conflict

0xbffde283…3385

0x34b655…2a6f

4 touches
1 conflict

0xb3fb9fb5…64dc

0x34b655…2a6f

4 touches
1 conflict

0x05e1eba1…6491

0x34b655…2a6f

4 touches
1 conflict

0x1501c918…f132

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x5b37bb6b…aaff

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 0x0d2de0f636…8fe6c6

← previous block·next block →recent activity