← previous blocknext block →recent activity

Analyzing

Block #86,784,915

27 transactions · 22 stateful · 2026-07-10 06:29:56 UTC

Parallelism

85/100

Blocked

32%

Avg conflicts / tx

0.33

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,784,915  ·  27 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

0x08c952c6…69b1

0x34b655…2a6f

4 touches
1 conflict

0x0a0cecef…4ed0

0x34b655…2a6f

4 touches
1 conflict

0x0a8f8b9c…3046

0x34b655…2a6f

4 touches
1 conflict

0x3347cbe5…846c

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x49ec39d3…0b07

0x34b655…2a6f

4 touches
1 conflict

0x49ec39d3…0b08

0x34b655…2a6f

4 touches
1 conflict

0xb6ed530c…d450

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

1 conflict on slot 0x08c952c6d6…8269b1

← previous block·next block →recent activity