← previous blocknext block →recent activity

Analyzing

Block #74,510,238

23 transactions · 15 stateful · 2026-05-14 09:33:04 UTC

Parallelism

74/100

Blocked

47%

Avg conflicts / tx

0.61

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,510,238  ·  23 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x380d926d…1034

0xd32edf…ff58

9 touches
10 conflicts

0x33018431…8f5e

0x188d58…ea8e

6 touches
3 conflicts

0x33018431…8f5c

0x188d58…ea8e

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x12309510…0ac2

0x000000…012a

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001d

0x1b6862…e19c

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: 0xd32edf66…9fff58

10 conflicts on slot 0x380d926d14…171034

← previous block·next block →recent activity