← previous blocknext block →recent activity

Analyzing

Block #86,243,823

20 transactions · 16 stateful · 2026-07-07 18:12:19 UTC

Parallelism

85/100

Blocked

44%

Avg conflicts / tx

0.5

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,243,823  ·  20 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

0xcc4f1f14…aa5f

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x19aa92ee…bfab

0x34b655…2a6f

4 touches
1 conflict

0x1eb0fab5…3517

0x34b655…2a6f

4 touches
1 conflict

0x216ffe66…1f94

0x34b655…2a6f

4 touches
1 conflict

0x397501e2…9a12

0x34b655…2a6f

4 touches
1 conflict

0x422d5490…52d9

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: Kuru Exchange: Market-MON/USDC

3 conflicts on slot 0xcc4f1f1446…7caa5f

← previous block·next block →recent activity