← previous blocknext block →recent activity

Analyzing

Block #74,761,208

39 transactions · 27 stateful · 2026-05-15 13:33:06 UTC

Parallelism

85/100

Blocked

52%

Avg conflicts / tx

0.74

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,761,208  ·  39 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x3fb18724…72d4

0xd32edf…ff58

11 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xa3aa46b3…6895

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x00000000…0002

0xab3526…fa38

6 touches
3 conflicts

0xf853eb8e…401e

0x34b655…2a6f

4 touches
1 conflict

0x7c403af1…31b1

0x3bd359…433a

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

15 conflicts on slot 0x3fb187243d…4572d4

← previous block·next block →recent activity