← previous blocknext block →recent activity

Analyzing

Block #73,978,891

15 transactions · 11 stateful · 2026-05-11 22:35:16 UTC

Parallelism

80/100

Blocked

36%

Avg conflicts / tx

0.47

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,978,891  ·  15 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

0xcb45d9d6…cb82

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…001a

0x1b6862…e19c

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x8524aa6f…5d80

0xd32edf…ff58

5 touches
3 conflicts

0x56a919c4…ab49

0xe7cd86…c82d

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xf537eaa0…73c8

0x065c9d…c394

4 touches
1 conflict

0x00f7e3b7…e015

0x188d58…ea8e

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: 0x1b68626d…2de19c

3 conflicts on slot 0xcb45d9d62a…b1cb82

← previous block·next block →recent activity