← previous blocknext block →recent activity

Analyzing

Block #74,306,630

23 transactions · 18 stateful · 2026-05-13 10:57:29 UTC

Parallelism

70/100

Blocked

44%

Avg conflicts / tx

1.04

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,306,630  ·  23 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xf1d72bbc…4e75

0xd32edf…ff58

13 touches
21 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xd29fbd52…f080

0x065c9d…c394

4 touches
1 conflict

0x30276c1c…47b4

0x2a68ba…90c5

4 touches
1 conflict

0xbb1747e2…f78b

0x34b655…2a6f

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0019

0x1b6862…e19c

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

21 conflicts on slot 0xf1d72bbccb…8d4e75

← previous block·next block →recent activity