← previous blocknext block →recent activity

Analyzing

Block #74,419,255

17 transactions · 12 stateful · 2026-05-13 23:26:48 UTC

Parallelism

82/100

Blocked

17%

Avg conflicts / tx

0.18

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,419,255  ·  17 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

0x95e2812d…bfcb

0xd32edf…ff58

5 touches
3 conflicts

0x93afca4c…b47b

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x2947020f…23cc

0x065c9d…c394

2 touches
0 conflicts

0x47b807a2…3307

0x065c9d…c394

2 touches
0 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

2 touches
0 conflicts

0x5ebf0cdb…4dd2

0x065c9d…c394

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

3 conflicts on slot 0x95e2812dd5…79bfcb

← previous block·next block →recent activity