← previous blocknext block →recent activity

Analyzing

Block #86,784,202

21 transactions · 15 stateful · 2026-07-10 06:25:10 UTC

Parallelism

76/100

Blocked

53%

Avg conflicts / tx

0.57

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,784,202  ·  21 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x0a0cecef…4ed0

0x34b655…2a6f

6 touches
3 conflicts

0x8a35acfb…d1a6

0xb1dbf0…c0d3

6 touches
3 conflicts

0x0e866e75…8fa9

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x5e02109f…c11b

0x34b655…2a6f

4 touches
1 conflict

0x71658d1a…f1ec

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