← previous blocknext block →recent activity

Analyzing

Block #75,297,455

20 transactions · 15 stateful · 2026-05-18 01:15:02 UTC

Parallelism

85/100

Blocked

27%

Avg conflicts / tx

0.2

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,297,455  ·  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

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0xc6417de0…2191

0xc8689a…ee79

4 touches
1 conflict

0x10c0f1ff…a3f5

0x111111…db61

2 touches
0 conflicts

0x9835db2a…294b

0x111111…db61

2 touches
0 conflicts

0xcb78f92f…9d79

0x111111…db61

2 touches
0 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

2 touches
0 conflicts

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: MarginAccount

1 conflict on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity