← previous blocknext block →recent activity

Analyzing

Block #74,766,657

42 transactions · 34 stateful · 2026-05-15 14:09:39 UTC

Parallelism

79/100

Blocked

68%

Avg conflicts / tx

1.64

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,766,657  ·  42 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

0x1a722e44…f6d1

0xd32edf…ff58

17 touches
36 conflicts

0x00000000…0002

0xab3526…fa38

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x0d0b2509…074d

0x3bd359…433a

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0xe6455d1f…1029

0x754704…b603

6 touches
3 conflicts

0xba5743c7…21c1

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

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

36 conflicts on slot 0x1a722e4491…25f6d1

← previous block·next block →recent activity