← previous blocknext block →recent activity

Analyzing

Block #86,964,098

22 transactions · 19 stateful · 2026-07-11 02:27:45 UTC

Parallelism

77/100

Blocked

47%

Avg conflicts / tx

0.55

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,964,098  ·  22 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xfaef08b1…0696

0x34b655…2a6f

6 touches
3 conflicts

0x49cbdb1b…bda4

0x065c9d…c394

6 touches
3 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xee4fe1f7…3ead

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0xb652c396…b8fa

0x34b655…2a6f

4 touches
1 conflict

0xa9511b78…07b5

0x40c49f…2af0

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: Perpl

3 conflicts on slot 0xfaef08b108…f90696

← previous block·next block →recent activity