← previous blocknext block →recent activity

Analyzing

Block #74,247,905

37 transactions · 28 stateful · 2026-05-13 04:26:54 UTC

Parallelism

81/100

Blocked

57%

Avg conflicts / tx

0.92

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,247,905  ·  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

0x3f2e6444…b892

0xd32edf…ff58

11 touches
15 conflicts

0x768cffcd…2648

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0000

0x63e48b…53f2

6 touches
3 conflicts

0x00000000…0002

0x63e48b…53f2

6 touches
3 conflicts

0x00000000…0004

0x63e48b…53f2

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x9a555477…19a8

0x754704…b603

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 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

15 conflicts on slot 0x3f2e6444ad…1bb892

← previous block·next block →recent activity