← previous blocknext block →recent activity

Analyzing

Block #86,668,349

24 transactions · 21 stateful · 2026-07-09 17:31:32 UTC

Parallelism

75/100

Blocked

43%

Avg conflicts / tx

0.67

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #86,668,349  ·  24 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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…000b

0x90c374…be45

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0x92385428…6941

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…000a

0x90c374…be45

8 touches
6 conflicts

0x93c58e4d…9b32

0x336ed4…c59c

6 touches
3 conflicts

0xc88f593e…5d93

0x336ed4…c59c

6 touches
3 conflicts

0x10a2bd5d…ad6d

0x8d1565…6723

6 touches
3 conflicts

0x7017d770…abbe

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: 0x90c3747c…0ebe45

6 conflicts on slot 0x0000000000…00000b

← previous block·next block →recent activity