← previous blocknext block →recent activity

Analyzing

Block #74,668,646

8 transactions · 6 stateful · 2026-05-15 03:15:12 UTC

Parallelism

63/100

Blocked

33%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,668,646  ·  8 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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xffe431af…8faa

0x065c9d…c394

4 touches
1 conflict

0x5c7c1424…5b93

0x065c9d…c394

3 touches
1 conflict

0x5a402406…7793

0x065c9d…c394

3 touches
1 conflict

0x2e75864f…b159

0x065c9d…c394

2 touches
0 conflicts

0x352b1c43…2358

0x065c9d…c394

2 touches
0 conflicts

0x4b31d9e7…1dad

0x065c9d…c394

2 touches
0 conflicts

0x5c8c6ab6…dc36

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: 0x065c9d28…a9c394

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity