← previous blocknext block →recent activity

Analyzing

Block #74,765,301

30 transactions · 19 stateful · 2026-05-15 14:00:32 UTC

Parallelism

90/100

Blocked

37%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,765,301  ·  30 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x664bf99e…0a8c

0x34b655…2a6f

6 touches
3 conflicts

0x5c0fd84a…c0bb

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0002

0xab3526…fa38

6 touches
3 conflicts

0x1760e128…4f7f

0xd32edf…ff58

5 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0x6f6fc26c…3e34

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

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: 0x34b6552d…112a6f

3 conflicts on slot 0x664bf99ec8…ec0a8c

← previous block·next block →recent activity