← previous blocknext block →recent activity

Analyzing

Block #74,392,636

12 transactions · 11 stateful · 2026-05-13 20:29:36 UTC

Parallelism

67/100

Blocked

45%

Avg conflicts / tx

0.67

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,392,636  ·  12 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xbc6fc2a1…a749

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x7188643d…1356

0x065c9d…c394

5 touches
3 conflicts

0x41755291…977f

0x065c9d…c394

4 touches
1 conflict

0x47b807a2…3307

0x065c9d…c394

4 touches
1 conflict

0x0178c2de…b37d

0x8d66a4…3095

4 touches
1 conflict

0x99522298…551a

0x065c9d…c394

4 touches
1 conflict

0x8a35acfb…d1a9

0x8d66a4…3095

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

3 conflicts on slot 0xbc6fc2a1ee…cfa749

← previous block·next block →recent activity