← previous blocknext block →recent activity

Analyzing

Block #74,319,668

16 transactions · 12 stateful · 2026-05-13 12:24:12 UTC

Parallelism

81/100

Blocked

42%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,319,668  ·  16 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

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0002

0x019883…2a9a

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x24968e6d…0132

0x065c9d…c394

4 touches
1 conflict

0x2497f4c6…110e

0x065c9d…c394

4 touches
1 conflict

0x489cb750…7069

0x065c9d…c394

4 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0x765c236f…ff45

0x2a68ba…90c5

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

3 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity