← previous blocknext block →recent activity

Analyzing

Block #74,342,672

15 transactions · 14 stateful · 2026-05-13 14:57:10 UTC

Parallelism

80/100

Blocked

50%

Avg conflicts / tx

0.8

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,342,672  ·  15 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

0x5c8c6ab6…dc36

0x065c9d…c394

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x4d3e58e0…a2d7

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0002

0xab3526…fa38

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0029

0x1b6862…e19c

4 touches
1 conflict

0x580c6fe7…0fe3

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: Market-MON/USDC

3 conflicts on slot 0x5c8c6ab6f0…86dc36

← previous block·next block →recent activity