← previous blocknext block →recent activity

Analyzing

Block #74,498,510

15 transactions · 12 stateful · 2026-05-14 08:14:14 UTC

Parallelism

73/100

Blocked

42%

Avg conflicts / tx

0.67

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,498,510  ·  15 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

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0x0a36af26…94c3

0x065c9d…c394

7 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x01e7b865…6e6f

0x188d58…ea8e

2 touches
0 conflicts

0x01e7b865…6e70

0x188d58…ea8e

2 touches
0 conflicts

0x4d95434b…ccb5

0x188d58…ea8e

2 touches
0 conflicts

0x807e1273…3c99

0x3bd359…433a

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

6 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity