← previous blocknext block →recent activity

Analyzing

Block #74,598,897

25 transactions · 19 stateful · 2026-05-14 19:29:33 UTC

Parallelism

80/100

Blocked

47%

Avg conflicts / tx

0.76

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,598,897  ·  25 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x0cb5b886…beee

0x34b655…2a6f

10 touches
10 conflicts

0xa472d565…9fe4

0x3bd359…433a

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x59ef13ba…2741

0x34b655…2a6f

6 touches
3 conflicts

0xeb0915f1…c150

0x34b655…2a6f

4 touches
1 conflict

0xbf25e763…684f

0x3bd359…433a

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

10 conflicts on slot 0x0cb5b886d8…77beee

← previous block·next block →recent activity