← previous blocknext block →recent activity

Analyzing

Block #74,427,476

23 transactions · 19 stateful · 2026-05-14 00:21:30 UTC

Parallelism

74/100

Blocked

42%

Avg conflicts / tx

0.87

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,427,476  ·  23 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

0xf6fd5476…5fea

0xd32edf…ff58

9 touches
10 conflicts

0xbad68552…e6bf

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x6af306bb…2e81

0x3bd359…433a

6 touches
3 conflicts

0xcb45d9d6…cb83

0x1b6862…e19c

4 touches
1 conflict

0x46cb45de…a568

0x188d58…ea8e

4 touches
1 conflict

0x1c354dc0…96de

0x754704…b603

4 touches
1 conflict

0xf91b744e…9117

0x754704…b603

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

10 conflicts on slot 0xf6fd54767d…3c5fea

← previous block·next block →recent activity