← previous blocknext block →recent activity

Analyzing

Block #86,780,980

20 transactions · 17 stateful · 2026-07-10 06:03:40 UTC

Parallelism

80/100

Blocked

47%

Avg conflicts / tx

0.7

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,780,980  ·  20 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

0x19ba76c3…6342

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0x8a35acfb…d1a9

0xb1dbf0…c0d3

6 touches
3 conflicts

0x0733be30…112f

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0x38e39eef…50bd

0x34b655…2a6f

4 touches
1 conflict

0x7d7ed9e4…4a59

0x34b655…2a6f

4 touches
1 conflict

0x7d7ed9e4…4a5a

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

6 conflicts on slot 0x19ba76c35e…d56342

← previous block·next block →recent activity