← previous blocknext block →recent activity

Analyzing

Block #74,649,829

20 transactions · 16 stateful · 2026-05-15 01:09:23 UTC

Parallelism

85/100

Blocked

38%

Avg conflicts / tx

0.45

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,649,829  ·  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

0xa4e3b3b1…0911

0x2a68ba…90c5

6 touches
3 conflicts

0xbb660b7e…a4e5

0xd32edf…ff58

5 touches
3 conflicts

0x5af720ab…d43e

0xa6afd3…d132

5 touches
3 conflicts

0x11b69a7e…334e

0xee8c0e…1242

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0xcb45d9d6…cb87

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

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

3 conflicts on slot 0xa4e3b3b1bb…130911

← previous block·next block →recent activity