← previous blocknext block →recent activity

Analyzing

Block #74,565,893

26 transactions · 15 stateful · 2026-05-14 15:48:32 UTC

Parallelism

85/100

Blocked

27%

Avg conflicts / tx

0.35

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,565,893  ·  26 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

0xbad68552…e6bf

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x742436a7…c4d4

0x34b655…2a6f

6 touches
3 conflicts

0xff57dec4…6482

0x34b655…2a6f

4 touches
1 conflict

0x1eb0fab5…3517

0x34b655…2a6f

4 touches
1 conflict

0x8e66c393…c9a2

0x34b655…2a6f

4 touches
1 conflict

0xe5e7089a…fb91

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

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

6 conflicts on slot 0xbad6855239…f0e6bf

← previous block·next block →recent activity