← previous blocknext block →recent activity

Analyzing

Block #74,392,261

16 transactions · 14 stateful · 2026-05-13 20:27:06 UTC

Parallelism

81/100

Blocked

36%

Avg conflicts / tx

0.31

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,392,261  ·  16 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

0x846f2172…fd54

0x0555e3…2b9c

4 touches
1 conflict

0x1c389468…6b0e

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x946dca5d…f959

0xd32edf…ff58

3 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

2 touches
0 conflicts

0x86e1625c…eb07

0x065c9d…c394

2 touches
0 conflicts

0xffe431af…8faa

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: 0x0555e30d…0d2b9c

1 conflict on slot 0x846f21722e…fdfd54

← previous block·next block →recent activity