← previous blocknext block →recent activity

Analyzing

Block #86,624,721

19 transactions · 16 stateful · 2026-07-09 12:38:49 UTC

Parallelism

79/100

Blocked

44%

Avg conflicts / tx

0.53

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,624,721  ·  19 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

0xffa7d0a4…b10a

0x40c49f…2af0

6 touches
3 conflicts

0x12094652…111b

0x34b655…2a6f

6 touches
3 conflicts

0x1d358edb…5fa0

0x34b655…2a6f

6 touches
3 conflicts

0x25b748bd…2e56

0x34b655…2a6f

6 touches
3 conflicts

0x85eb1316…bb9e

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…641f

0x34b655…2a6f

6 touches
3 conflicts

0xe969e870…e4ff

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x40c49f…2af0

6 touches
3 conflicts

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: 0x40c49f17…d22af0

3 conflicts on slot 0xffa7d0a419…63b10a

← previous block·next block →recent activity