← previous blocknext block →recent activity

Analyzing

Block #74,920,285

22 transactions · 18 stateful · 2026-05-16 07:14:40 UTC

Parallelism

68/100

Blocked

44%

Avg conflicts / tx

1.05

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,920,285  ·  22 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

0x00000000…0002

0xab3526…fa38

14 touches
21 conflicts

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xd996735f…8733

0x1b6862…e19c

4 touches
1 conflict

0xdd68e1bd…6bf7

0xd32edf…ff58

3 touches
1 conflict

0x87d13911…d4c1

0x065c9d…c394

2 touches
0 conflicts

0x8c74e778…ff0a

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: 0xab35264b…1cfa38

21 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity