← previous blocknext block →recent activity

Analyzing

Block #74,774,272

26 transactions · 16 stateful · 2026-05-15 15:00:39 UTC

Parallelism

88/100

Blocked

38%

Avg conflicts / tx

0.31

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,774,272  ·  26 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

0x765c236f…ff45

0x2a68ba…90c5

6 touches
3 conflicts

0x343f9c37…5cc9

0xd32edf…ff58

5 touches
3 conflicts

0xc0f29314…17f9

0x1b6862…e19c

4 touches
1 conflict

0x1a8920f3…4a31

0x065c9d…c394

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

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: 0x2a68ba18…8e90c5

3 conflicts on slot 0x765c236f2d…b5ff45

← previous block·next block →recent activity