← previous blocknext block →recent activity

Analyzing

Block #91,259,488

19 transactions · 16 stateful · 2026-07-29 05:23:26 UTC

Parallelism

89/100

Blocked

38%

Avg conflicts / tx

0.32

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #91,259,488  ·  19 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

4 touches
1 conflict

0x00000000…00c9

0x34b655…2a6f

4 touches
1 conflict

0x07d8b1e8…78c6

0x34b655…2a6f

4 touches
1 conflict

0x343bff7a…acac

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x50ea66a4…0b5d

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x7462b8f2…6312

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

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity