← previous blocknext block →recent activity

Analyzing

Block #86,629,063

21 transactions · 18 stateful · 2026-07-09 13:07:49 UTC

Parallelism

76/100

Blocked

44%

Avg conflicts / tx

0.71

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,629,063  ·  21 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

0x4a4c3d20…bd65

0x3bd359…433a

10 touches
10 conflicts

0x00000000…0000

0x4a92f8…f3d6

10 touches
10 conflicts

0x0db0aaac…e94d

0x43cf54…7777

10 touches
10 conflicts

0x00000000…0001

0x4a92f8…f3d6

8 touches
6 conflicts

0x00000000…0002

0xfe2b47…c052

6 touches
3 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0xa6afd3…d132

4 touches
1 conflict

0x3c3718ac…fc3f

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: Wrapped MON (WMON)

10 conflicts on slot 0x4a4c3d20ec…42bd65

← previous block·next block →recent activity