← previous blocknext block →recent activity

Analyzing

Block #74,686,762

19 transactions · 17 stateful · 2026-05-15 05:15:54 UTC

Parallelism

89/100

Blocked

18%

Avg conflicts / tx

0.16

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,686,762  ·  19 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xd0e8ff37…265a

0x065c9d…c394

4 touches
1 conflict

0xee98fc49…1f9e

0x065c9d…c394

4 touches
1 conflict

0xa02838a3…bc54

0x34b655…2a6f

4 touches
1 conflict

0x5822b55c…e54a

0x065c9d…c394

3 touches
1 conflict

0x94ee5c35…54f9

0x065c9d…c394

3 touches
1 conflict

0x47b807a2…3307

0x065c9d…c394

2 touches
0 conflicts

0x991ade75…938e

0x065c9d…c394

2 touches
0 conflicts

0xcacefddf…3ef1

0x065c9d…c394

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 0xd0e8ff3751…73265a

← previous block·next block →recent activity