← previous blocknext block →recent activity

Analyzing

Block #74,762,904

37 transactions · 24 stateful · 2026-05-15 13:44:30 UTC

Parallelism

81/100

Blocked

42%

Avg conflicts / tx

0.7

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,762,904  ·  37 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

0x62fd07fe…fcb7

0xd32edf…ff58

13 touches
21 conflicts

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x0d0b2509…074d

0x3bd359…433a

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0xe6455d1f…1029

0x754704…b603

4 touches
1 conflict

0xb9868b52…c77f

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: 0xd32edf66…9fff58

21 conflicts on slot 0x62fd07fe31…f5fcb7

← previous block·next block →recent activity