← previous blocknext block →recent activity

Analyzing

Block #74,763,137

44 transactions · 28 stateful · 2026-05-15 13:46:05 UTC

Parallelism

89/100

Blocked

46%

Avg conflicts / tx

0.61

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,763,137  ·  44 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

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xb9868b52…c77f

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xc0df0979…9cf2

0xd32edf…ff58

5 touches
3 conflicts

0x8db1e0f2…2fcf

0x34b655…2a6f

4 touches
1 conflict

0xa9988419…9f45

0x34b655…2a6f

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

10 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity