← previous blocknext block →recent activity

Analyzing

Block #74,369,958

10 transactions · 8 stateful · 2026-05-13 17:58:37 UTC

Parallelism

70/100

Blocked

25%

Avg conflicts / tx

0.2

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,369,958  ·  10 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x07bfd719…802d

0x065c9d…c394

2 touches
0 conflicts

0xb4f1e77e…d4b9

0x065c9d…c394

2 touches
0 conflicts

0xeb0fd275…2be9

0x065c9d…c394

2 touches
0 conflicts

0xf8c1eb93…c8cd

0x065c9d…c394

2 touches
0 conflicts

0x194f2c02…19e6

0x2a68ba…90c5

2 touches
0 conflicts

0x968bdacb…f461

0x2a68ba…90c5

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