← previous blocknext block →recent activity

Analyzing

Block #86,688,757

16 transactions · 10 stateful · 2026-07-09 19:47:47 UTC

Parallelism

88/100

Blocked

20%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #86,688,757  ·  16 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xfbffb606…d70c

0x34b655…2a6f

4 touches
1 conflict

0xa680b0df…5e60

0x34b655…2a6f

4 touches
1 conflict

0xb2fa1675…4e07

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0x08cc68a2…2a59

0x34b655…2a6f

4 touches
1 conflict

0x273c2a35…7513

0x34b655…2a6f

4 touches
1 conflict

0x30c67647…8a4c

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 0xfbffb6064d…a2d70c

← previous block·next block →recent activity