← previous blocknext block →recent activity

Analyzing

Block #74,377,225

20 transactions · 15 stateful · 2026-05-13 18:47:01 UTC

Parallelism

75/100

Blocked

47%

Avg conflicts / tx

0.7

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,377,225  ·  20 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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xa02838a3…bc54

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0002

0xab3526…fa38

6 touches
3 conflicts

0x28c180e1…f1e2

0x34b655…2a6f

6 touches
3 conflicts

0xa486f342…64d5

0x34b655…2a6f

6 touches
3 conflicts

0xe35ce909…56db

0x34b655…2a6f

6 touches
3 conflicts

0x4d3e58e0…a2d7

0x34b655…2a6f

4 touches
1 conflict

0x757254ae…d917

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

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity