← previous blocknext block →recent activity

Analyzing

Block #74,351,743

32 transactions · 24 stateful · 2026-05-13 15:57:25 UTC

Parallelism

81/100

Blocked

38%

Avg conflicts / tx

0.72

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,351,743  ·  32 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

0x84dddddb…9267

0xd32edf…ff58

11 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x38c47502…1005

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0019

0x1b6862…e19c

6 touches
3 conflicts

0xcb45d9d6…cb81

0x1b6862…e19c

6 touches
3 conflicts

0xf91b744e…9117

0x754704…b603

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

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 0x84dddddb3e…409267

← previous block·next block →recent activity