← previous blocknext block →recent activity

Analyzing

Block #74,430,016

26 transactions · 20 stateful · 2026-05-14 00:38:26 UTC

Parallelism

65/100

Blocked

50%

Avg conflicts / tx

0.73

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,430,016  ·  26 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x655572c4…8d61

0xd32edf…ff58

9 touches
10 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0xe6455d1f…1029

0x754704…b603

6 touches
3 conflicts

0x0d0b2509…074d

0x3bd359…433a

6 touches
3 conflicts

0x00000000…002b

0x1b6862…e19c

4 touches
1 conflict

0x2ce2d49e…d188

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0xf8127de7…d5ec

0x3bd359…433a

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

10 conflicts on slot 0x655572c4ad…2d8d61

← previous block·next block →recent activity