← previous blocknext block →recent activity

Analyzing

Block #74,252,657

21 transactions · 18 stateful · 2026-05-13 04:58:29 UTC

Parallelism

76/100

Blocked

56%

Avg conflicts / tx

1.05

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,252,657  ·  21 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x30276c1c…47b4

0x2a68ba…90c5

10 touches
10 conflicts

0x768cffcd…2648

0x34b655…2a6f

8 touches
6 conflicts

0xf823e97f…2ee6

0x065c9d…c394

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x1b5d2e60…99b5

0x34b655…2a6f

4 touches
1 conflict

0x29acbf40…28b7

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: 0x2a68ba18…8e90c5

10 conflicts on slot 0x30276c1c08…7247b4

← previous block·next block →recent activity