← previous blocknext block →recent activity

Analyzing

Block #85,918,649

26 transactions · 25 stateful · 2026-07-06 06:01:35 UTC

Parallelism

62/100

Blocked

60%

Avg conflicts / tx

2.08

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #85,918,649  ·  26 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x90c374…be45

20 touches
45 conflicts

0x00000000…000b

0x90c374…be45

20 touches
45 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0xafd867b7…2b2e

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x40970e69…da50

0x69df8a…6292

4 touches
1 conflict

0x8cf3d245…1d0d

0x69df8a…6292

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

45 conflicts on slot 0x0000000000…00000a

← previous block·next block →recent activity