← previous blocknext block →recent activity

Analyzing

Block #74,415,566

8 transactions · 7 stateful · 2026-05-13 23:02:15 UTC

Parallelism

75/100

Blocked

43%

Avg conflicts / tx

0.38

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

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

0xffe431af…8faa

0x065c9d…c394

4 touches
1 conflict

0xb245fe36…d765

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x93d1c1c5…b4d0

0x065c9d…c394

3 touches
1 conflict

0x203c7c63…1484

0x065c9d…c394

3 touches
1 conflict

0x64c4114a…fd48

0x065c9d…c394

2 touches
0 conflicts

0x6b084154…4b36

0x065c9d…c394

2 touches
0 conflicts

0xcd53e2c7…fe6e

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

1 conflict on slot 0xffe431af56…838faa

← previous block·next block →recent activity