← previous blocknext block →recent activity

Analyzing

Block #94,200,455

22 transactions · 21 stateful · 2026-08-08 12:03:22 UTC

Parallelism

73/100

Blocked

38%

Avg conflicts / tx

0.82

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #94,200,455  ·  22 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xbd347fb8…1c08

0x065c9d…c394

12 touches
15 conflicts

0xa1087a5c…66c4

0x754704…b603

12 touches
15 conflicts

0x0778475b…bd75

0x2a68ba…90c5

12 touches
15 conflicts

0x3d9eb674…b3fb

0x754704…b603

6 touches
3 conflicts

0x4c1fbdf6…953d

0x754704…b603

4 touches
1 conflict

0x058d5849…bbd6

0x34b655…2a6f

4 touches
1 conflict

0x206f4379…e08a

0x34b655…2a6f

4 touches
1 conflict

0x4cabb80a…46bf

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

15 conflicts on slot 0xbd347fb838…a01c08

← previous block·next block →recent activity