← previous blocknext block →recent activity

Analyzing

Block #74,796,544

23 transactions · 16 stateful · 2026-05-15 17:29:25 UTC

Parallelism

87/100

Blocked

38%

Avg conflicts / tx

0.3

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,796,544  ·  23 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xa02838a3…bc54

0x34b655…2a6f

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x47b807a2…3307

0x065c9d…c394

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001a

0x1b6862…e19c

4 touches
1 conflict

0xcb45d9d6…cb82

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

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

3 conflicts on slot 0xa02838a385…ffbc54

← previous block·next block →recent activity