← previous blocknext block →recent activity

Analyzing

Block #74,331,389

16 transactions · 11 stateful · 2026-05-13 13:42:09 UTC

Parallelism

88/100

Blocked

18%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,331,389  ·  16 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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x729c91b8…9537

0x188d58…ea8e

4 touches
1 conflict

0x56a919c4…ab49

0xee8c0e…1242

4 touches
1 conflict

0x729c91b8…9538

0x188d58…ea8e

4 touches
1 conflict

0x00000000…0019

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0029

0x1b6862…e19c

2 touches
0 conflicts

0xba5743c7…21c0

0x1b6862…e19c

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 0x0000000000…00003d

← previous block·next block →recent activity