← previous blocknext block →recent activity

Analyzing

Block #74,415,758

15 transactions · 13 stateful · 2026-05-13 23:03:32 UTC

Parallelism

73/100

Blocked

38%

Avg conflicts / tx

0.53

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,415,758  ·  15 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

0x00000000…0002

0xab3526…fa38

8 touches
6 conflicts

0xc6417de0…2191

0xc8689a…ee79

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x3ca4b2f1…fbb0

0x065c9d…c394

2 touches
0 conflicts

0x4ea0a5ca…d0d8

0x065c9d…c394

2 touches
0 conflicts

0xb6635423…a29d

0x065c9d…c394

2 touches
0 conflicts

0xffe431af…8faa

0x065c9d…c394

2 touches
0 conflicts

0x99f666e3…b2a2

0x3bd359…433a

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: 0xab35264b…1cfa38

6 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity