← previous blocknext block →recent activity

Analyzing

Block #74,647,007

28 transactions · 14 stateful · 2026-05-15 00:50:40 UTC

Parallelism

86/100

Blocked

36%

Avg conflicts / tx

0.29

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,647,007  ·  28 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

0x1318b705…7ebe

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0xf58eca50…59fd

0x1b6862…e19c

4 touches
1 conflict

0x765c236f…ff45

0x2a68ba…90c5

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x5bbb252b…38d2

0x065c9d…c394

3 touches
1 conflict

0x00000000…0004

0x094452…0a09

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

6 conflicts on slot 0x1318b7053b…757ebe

← previous block·next block →recent activity