← previous blocknext block →recent activity

Analyzing

Block #74,308,605

30 transactions · 27 stateful · 2026-05-13 11:10:38 UTC

Parallelism

83/100

Blocked

56%

Avg conflicts / tx

0.83

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,308,605  ·  30 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

0x8a8d81ce…5d56

0xd32edf…ff58

9 touches
10 conflicts

0xbb1747e2…f78b

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x0eac6378…36f4

0x34b655…2a6f

6 touches
3 conflicts

0x01e7b865…6e6e

0x188d58…ea8e

4 touches
1 conflict

0x18aed20c…48f3

0x000000…012a

4 touches
1 conflict

0xd77e90ec…8c04

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

10 conflicts on slot 0x8a8d81ce43…995d56

← previous block·next block →recent activity