← previous blocknext block →recent activity

Analyzing

Block #74,630,774

14 transactions · 13 stateful · 2026-05-14 23:02:33 UTC

Parallelism

86/100

Blocked

31%

Avg conflicts / tx

0.36

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,630,774  ·  14 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0xffe431af…8faa

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0xd9ea5418…655b

0xd32edf…ff58

3 touches
1 conflict

0x4413922e…c3e3

0x065c9d…c394

3 touches
1 conflict

0x9194f4a3…10b8

0x754704…b603

2 touches
0 conflicts

0xa1087a5c…66c4

0x754704…b603

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: 0x34b6552d…112a6f

1 conflict on slot 0xea02471df2…601542

← previous block·next block →recent activity