← previous blocknext block →recent activity

Analyzing

Block #74,240,709

14 transactions · 11 stateful · 2026-05-13 03:39:03 UTC

Parallelism

86/100

Blocked

27%

Avg conflicts / tx

0.21

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,240,709  ·  14 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x768cffcd…2648

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x98314882…05c6

0xd32edf…ff58

3 touches
1 conflict

0x17d96b91…65ff

0x065c9d…c394

2 touches
0 conflicts

0x2a354a63…0515

0x065c9d…c394

2 touches
0 conflicts

0x36ca42ca…2a9d

0x065c9d…c394

2 touches
0 conflicts

0x879a41fb…249e

0x065c9d…c394

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: 0x34b6552d…112a6f

1 conflict on slot 0x768cffcdb0…d12648

← previous block·next block →recent activity