← previous blocknext block →recent activity

Analyzing

Block #74,918,631

18 transactions · 14 stateful · 2026-05-16 07:03:37 UTC

Parallelism

61/100

Blocked

50%

Avg conflicts / tx

1.22

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,918,631  ·  18 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

0x6c911565…62f6

0xd32edf…ff58

13 touches
21 conflicts

0x87d7c0b8…7364

0x065c9d…c394

4 touches
1 conflict

0x30276c1c…47b4

0x2a68ba…90c5

4 touches
1 conflict

0x931cada7…dbc8

0x065c9d…c394

3 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0015

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…001d

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…002d

0x1b6862…e19c

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

21 conflicts on slot 0x6c9115653a…4062f6

← previous block·next block →recent activity