← previous blocknext block →recent activity

Analyzing

Block #86,103,339

23 transactions · 19 stateful · 2026-07-07 02:34:18 UTC

Parallelism

78/100

Blocked

42%

Avg conflicts / tx

0.39

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,103,339  ·  23 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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xac33ff75…077b

0xfa32f9…f3f0

4 touches
1 conflict

0xec0e0220…cb90

0x34b655…2a6f

4 touches
1 conflict

0x99f666e3…b2a2

0x3bd359…433a

4 touches
1 conflict

0x00000000…003d

0x40c49f…2af0

4 touches
1 conflict

0xffa7d0a4…b10a

0x40c49f…2af0

4 touches
1 conflict

0x9194f4a3…10b8

0x754704…b603

4 touches
1 conflict

0x00000000…0000

0xfa32f9…f3f0

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 0x0000000000…00003d

← previous block·next block →recent activity