← previous blocknext block →recent activity

Analyzing

Block #74,601,148

34 transactions · 24 stateful · 2026-05-14 19:44:48 UTC

Parallelism

88/100

Blocked

38%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,601,148  ·  34 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xe6455d1f…1029

0x754704…b603

8 touches
6 conflicts

0x0d0b2509…074d

0x3bd359…433a

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x18b11fba…c92a

0x34b655…2a6f

6 touches
3 conflicts

0x08943ea2…ed03

0x754704…b603

4 touches
1 conflict

0x24968e6d…0132

0x065c9d…c394

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: 0x754704bc…afb603

6 conflicts on slot 0xe6455d1fbe…eb1029

← previous block·next block →recent activity