← previous blocknext block →recent activity

Analyzing

Block #86,342,113

19 transactions · 14 stateful · 2026-07-08 05:08:40 UTC

Parallelism

84/100

Blocked

43%

Avg conflicts / tx

0.47

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,342,113  ·  19 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

0xcc8faac2…c766

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xa1830b71…6cd6

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0002

0x04fdea…47d7

4 touches
1 conflict

0x20d4cbf5…168a

0x065c9d…c394

4 touches
1 conflict

0x18cf3003…51d1

0x065c9d…c394

4 touches
1 conflict

0x2697123c…8526

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 0xcc8faac238…88c766

← previous block·next block →recent activity