← previous blocknext block →recent activity

Analyzing

Block #74,423,124

25 transactions · 19 stateful · 2026-05-13 23:52:32 UTC

Parallelism

76/100

Blocked

42%

Avg conflicts / tx

0.84

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,423,124  ·  25 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x23125d2a…fe50

0xd32edf…ff58

11 touches
15 conflicts

0x6af306bb…2e81

0x3bd359…433a

6 touches
3 conflicts

0x46cb45de…a566

0x188d58…ea8e

6 touches
3 conflicts

0x46cb45de…a568

0x188d58…ea8e

6 touches
3 conflicts

0x00000000…001b

0x1b6862…e19c

6 touches
3 conflicts

0xcb45d9d6…cb83

0x1b6862…e19c

6 touches
3 conflicts

0x1c354dc0…96de

0x754704…b603

6 touches
3 conflicts

0xf91b744e…9117

0x754704…b603

6 touches
3 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

15 conflicts on slot 0x23125d2aae…4efe50

← previous block·next block →recent activity