← previous blocknext block →recent activity

Analyzing

Block #74,010,421

8 transactions · 6 stateful · 2026-05-12 02:07:25 UTC

Parallelism

75/100

Blocked

33%

Avg conflicts / tx

0.25

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,010,421  ·  8 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

0xf3808e5a…dbfb

0x34b655…2a6f

4 touches
1 conflict

0x8a35acfb…d1ac

0x8d66a4…3095

4 touches
1 conflict

0xe89e1a22…ce49

0x8d66a4…3095

4 touches
1 conflict

0x9ea57326…329f

0x34b655…2a6f

4 touches
1 conflict

0x556f7219…067a

0x065c9d…c394

2 touches
0 conflicts

0xad4675c3…f0f2

0x065c9d…c394

2 touches
0 conflicts

0xd55b8dc8…59e7

0x065c9d…c394

2 touches
0 conflicts

0xf2f7c61f…a067

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: 0x34b6552d…112a6f

1 conflict on slot 0xf3808e5ac6…eadbfb

← previous block·next block →recent activity