← previous blocknext block →recent activity

Analyzing

Block #86,487,729

22 transactions · 18 stateful · 2026-07-08 21:21:52 UTC

Parallelism

59/100

Blocked

50%

Avg conflicts / tx

1.68

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #86,487,729  ·  22 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x00000000…0001

0xa2c1a0…7201

18 touches
36 conflicts

0xd35bb5ac…3586

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x2b964c40…078e

0x065c9d…c394

2 touches
0 conflicts

0xaff271e8…60d2

0x065c9d…c394

2 touches
0 conflicts

0xb1918588…db13

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0013

0x1b6862…e19c

2 touches
0 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: 0xa2c1a021…627201

36 conflicts on slot 0x0000000000…000001

← previous block·next block →recent activity