← previous blocknext block →recent activity

Analyzing

Block #74,691,070

7 transactions · 7 stateful · 2026-05-15 05:44:33 UTC

Parallelism

71/100

Blocked

14%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,691,070  ·  7 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

0x41755291…977f

0x065c9d…c394

4 touches
1 conflict

0x47b807a2…3307

0x065c9d…c394

2 touches
0 conflicts

0x493a5e32…b317

0x065c9d…c394

2 touches
0 conflicts

0x61e0e949…ff7a

0x065c9d…c394

2 touches
0 conflicts

0x85a4c222…e51b

0x065c9d…c394

2 touches
0 conflicts

0x93ee09ee…fd1b

0x065c9d…c394

2 touches
0 conflicts

0xa472e5b4…8417

0x065c9d…c394

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

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity