← previous blocknext block →recent activity

Analyzing

Block #74,298,813

19 transactions · 17 stateful · 2026-05-13 10:05:30 UTC

Parallelism

79/100

Blocked

29%

Avg conflicts / tx

0.47

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,298,813  ·  19 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

0xaa082f95…9cca

0xd32edf…ff58

7 touches
6 conflicts

0x7b7bcac3…8fbf

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x1b5d2e60…99b5

0x34b655…2a6f

4 touches
1 conflict

0x88ddd628…7d59

0x34b655…2a6f

4 touches
1 conflict

0x85a88798…f85e

0x34b655…2a6f

4 touches
1 conflict

0x6c22c70d…33c8

0x34b655…2a6f

4 touches
1 conflict

0x7cee1be1…e770

0x34b655…2a6f

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

6 conflicts on slot 0xaa082f9553…4a9cca

← previous block·next block →recent activity