← previous blocknext block →recent activity

Analyzing

Block #74,420,646

32 transactions · 24 stateful · 2026-05-13 23:36:01 UTC

Parallelism

84/100

Blocked

42%

Avg conflicts / tx

0.59

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,420,646  ·  32 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

0xf3981be5…2c47

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xe5e7089a…fb91

0x34b655…2a6f

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0xf3d10975…0d07

0x34b655…2a6f

8 touches
6 conflicts

0x404a5c08…fa59

0xd32edf…ff58

7 touches
6 conflicts

0xa678cb89…4abd

0x34b655…2a6f

6 touches
3 conflicts

0xffe431af…8faa

0x065c9d…c394

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

10 conflicts on slot 0xf3981be56e…f02c47

← previous block·next block →recent activity