← previous blocknext block →recent activity

Analyzing

Block #74,427,284

23 transactions · 18 stateful · 2026-05-14 00:20:16 UTC

Parallelism

78/100

Blocked

44%

Avg conflicts / tx

0.7

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

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

0x6de200ac…41e4

0xd32edf…ff58

9 touches
10 conflicts

0xbad68552…e6bf

0x34b655…2a6f

6 touches
3 conflicts

0x6af306bb…2e81

0x3bd359…433a

4 touches
1 conflict

0xea02471d…1539

0x34b655…2a6f

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x941a33ca…2f92

0xd18b7e…414b

4 touches
1 conflict

0xf26eda05…0203

0xd18b7e…414b

4 touches
1 conflict

0xcb8c97d5…6339

0x188d58…ea8e

2 touches
0 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

10 conflicts on slot 0x6de200acfd…ee41e4

← previous block·next block →recent activity