← previous blocknext block →recent activity

Analyzing

Block #74,331,463

21 transactions · 14 stateful · 2026-05-13 13:42:38 UTC

Parallelism

90/100

Blocked

14%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,331,463  ·  21 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

0x8a35acfb…d1a7

0x8d66a4…3095

4 touches
1 conflict

0xa94cf3f4…554c

0x8d66a4…3095

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x0b28bf77…e53a

0x34b655…2a6f

4 touches
1 conflict

0x3bbba474…c545

0x065c9d…c394

2 touches
0 conflicts

0xb19629f8…81b3

0x065c9d…c394

2 touches
0 conflicts

0xd834ba82…3293

0x065c9d…c394

2 touches
0 conflicts

0xffe431af…8faa

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: 0x8d66a43f…113095

1 conflict on slot 0x8a35acfbc1…6bd1a7

← previous block·next block →recent activity