← previous blocknext block →recent activity

Analyzing

Block #74,510,734

18 transactions · 14 stateful · 2026-05-14 09:36:26 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,510,734  ·  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

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0x78067279…d187

0x34b655…2a6f

6 touches
3 conflicts

0x96f39b8e…f795

0x34b655…2a6f

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0xa6464996…3af9

0x34b655…2a6f

4 touches
1 conflict

0xb409e204…89ac

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xd895ee0b…d301

0x34b655…2a6f

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

21 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity