← previous blocknext block →recent activity

Analyzing

Block #86,798,413

26 transactions · 18 stateful · 2026-07-10 08:00:04 UTC

Parallelism

88/100

Blocked

33%

Avg conflicts / tx

0.27

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,798,413  ·  26 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xf79df061…e005

0xe52b14…7230

6 touches
3 conflicts

0xfaef08b1…0696

0x34b655…2a6f

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0x0b9f02c4…6fec

0x34b655…2a6f

4 touches
1 conflict

0x9a3068dd…18f0

0x34b655…2a6f

4 touches
1 conflict

0x9a3068dd…18f1

0x34b655…2a6f

4 touches
1 conflict

0x9aa29e0c…eb5b

0x34b655…2a6f

4 touches
1 conflict

0xaaae1618…1ada

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: 0xe52b1424…bb7230

3 conflicts on slot 0xf79df061c7…91e005

← previous block·next block →recent activity