← previous blocknext block →recent activity

Analyzing

Block #74,510,151

26 transactions · 21 stateful · 2026-05-14 09:32:29 UTC

Parallelism

73/100

Blocked

67%

Avg conflicts / tx

1.54

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,510,151  ·  26 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x765c236f…ff45

0x2a68ba…90c5

12 touches
15 conflicts

0xa65bb2f6…5c29

0xd32edf…ff58

11 touches
15 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0xffe431af…8faa

0x065c9d…c394

6 touches
3 conflicts

0xbb3d6581…32d5

0x065c9d…c394

5 touches
3 conflicts

0x56a919c4…ab49

0xee8c0e…1242

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: 0x2a68ba18…8e90c5

15 conflicts on slot 0x765c236f2d…b5ff45

← previous block·next block →recent activity