← previous blocknext block →recent activity

Analyzing

Block #74,482,184

15 transactions · 11 stateful · 2026-05-14 06:25:39 UTC

Parallelism

80/100

Blocked

36%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,482,184  ·  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

0x4aa4f53b…899f

0x188d58…ea8e

6 touches
3 conflicts

0x33018431…8f5e

0x188d58…ea8e

6 touches
3 conflicts

0x33018431…8f5c

0x188d58…ea8e

6 touches
3 conflicts

0x4aa4f53b…89a0

0x188d58…ea8e

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x6f0ab2e7…d3b1

0xd32edf…ff58

5 touches
3 conflicts

0x5dbda192…192d

0x754704…b603

4 touches
1 conflict

0x00000000…0013

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: 0x188d586d…f9ea8e

3 conflicts on slot 0x4aa4f53bc4…b2899f

← previous block·next block →recent activity