← previous blocknext block →recent activity

Analyzing

Block #74,505,121

30 transactions · 15 stateful · 2026-05-14 08:58:36 UTC

Parallelism

77/100

Blocked

53%

Avg conflicts / tx

0.73

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,505,121  ·  30 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x38c6c29d…0662

0xd32edf…ff58

11 touches
15 conflicts

0x00000000…0003

0x116e7d…d8f1

8 touches
6 conflicts

0x00000000…0000

0x116e7d…d8f1

8 touches
6 conflicts

0x00000000…0001

0x116e7d…d8f1

8 touches
6 conflicts

0xb7143610…adc4

0x3bd359…433a

8 touches
6 conflicts

0x692a4122…76b8

0x350035…7777

8 touches
6 conflicts

0xadafd6ba…1fe0

0x699abc…6a3b

4 touches
1 conflict

0xd06cc746…27e4

0x350035…7777

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

15 conflicts on slot 0x38c6c29d9f…b20662

← previous block·next block →recent activity