← previous blocknext block →recent activity

Analyzing

Block #86,753,957

28 transactions · 20 stateful · 2026-07-10 03:03:18 UTC

Parallelism

86/100

Blocked

35%

Avg conflicts / tx

0.32

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,753,957  ·  28 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

0x74550a4b…68bd

0x34b655…2a6f

6 touches
3 conflicts

0x2b54cadb…4425

0xd18b7e…414b

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x102ce3d3…2d5c

0x40c49f…2af0

4 touches
1 conflict

0xdbd174e4…b6f8

0x34b655…2a6f

4 touches
1 conflict

0xffe427b5…5d4d

0x065c9d…c394

4 touches
1 conflict

0x01e7b865…6e6d

0x188d58…ea8e

4 touches
1 conflict

0xd98b3c10…67b8

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 0x74550a4bea…1f68bd

← previous block·next block →recent activity