← previous blocknext block →recent activity

Analyzing

Block #86,713,140

21 transactions · 17 stateful · 2026-07-09 22:30:26 UTC

Parallelism

81/100

Blocked

41%

Avg conflicts / tx

0.38

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,713,140  ·  21 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

0x8a35acfb…d1a7

0xb1dbf0…c0d3

6 touches
3 conflicts

0x8a35acfb…d1a8

0xb1dbf0…c0d3

6 touches
3 conflicts

0x52e69143…95ad

0x065c9d…c394

4 touches
1 conflict

0xce827910…ff22

0x065c9d…c394

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x793aa64d…b09c

0x34b655…2a6f

4 touches
1 conflict

0x793aa64d…b09d

0x34b655…2a6f

4 touches
1 conflict

0x92385428…6941

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: 0xb1dbf05f…b1c0d3

3 conflicts on slot 0x8a35acfbc1…6bd1a7

← previous block·next block →recent activity