← previous blocknext block →recent activity

Analyzing

Block #74,369,570

10 transactions · 9 stateful · 2026-05-13 17:56:02 UTC

Parallelism

70/100

Blocked

22%

Avg conflicts / tx

0.3

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,369,570  ·  10 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

0x7b62ad43…3066

0x065c9d…c394

3 touches
1 conflict

0xbc123464…6ac2

0x065c9d…c394

3 touches
1 conflict

0x6a1938e1…d49f

0x065c9d…c394

3 touches
1 conflict

0x4d97ee42…1160

0x065c9d…c394

2 touches
0 conflicts

0x61d1f176…bc43

0x065c9d…c394

2 touches
0 conflicts

0xbf2efc1f…1f68

0x065c9d…c394

2 touches
0 conflicts

0xf026380e…e65e

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