← previous blocknext block →recent activity

Analyzing

Block #86,956,713

26 transactions · 21 stateful · 2026-07-11 01:38:22 UTC

Parallelism

73/100

Blocked

48%

Avg conflicts / tx

1.23

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #86,956,713  ·  26 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x1941b441…5889

0x34b655…2a6f

14 touches
21 conflicts

0xfaef08b1…0696

0x34b655…2a6f

10 touches
10 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0x6c7e1952…d9c9

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0xaba6578d…bd48

0x34b655…2a6f

6 touches
3 conflicts

0xd1c5aeea…ee0a

0x34b655…2a6f

6 touches
3 conflicts

0xdb3937e8…23cb

0x34b655…2a6f

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

21 conflicts on slot 0x1941b4413e…0c5889

← previous block·next block →recent activity