← previous blocknext block →recent activity

Analyzing

Block #74,385,961

19 transactions · 13 stateful · 2026-05-13 19:45:10 UTC

Parallelism

79/100

Blocked

23%

Avg conflicts / tx

0.21

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,385,961  ·  19 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

0x47b807a2…3307

0x065c9d…c394

4 touches
1 conflict

0x0872abbe…9c39

0x2a68ba…90c5

4 touches
1 conflict

0xe6d27440…c68c

0x065c9d…c394

3 touches
1 conflict

0xaf550028…54f7

0x065c9d…c394

3 touches
1 conflict

0xc7d7a5a0…4854

0xd32edf…ff58

3 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…001a

0x1b6862…e19c

2 touches
0 conflicts

0x09000000…0001

0x000000…1000

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 0x47b807a243…c53307

← previous block·next block →recent activity