← previous blocknext block →recent activity

Analyzing

Block #74,767,900

30 transactions · 22 stateful · 2026-05-15 14:18:00 UTC

Parallelism

83/100

Blocked

55%

Avg conflicts / tx

0.93

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,767,900  ·  30 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

0x3b9900ff…cbbd

0xd32edf…ff58

9 touches
10 conflicts

0xb9868b52…c77f

0x34b655…2a6f

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…002a

0x1b6862…e19c

6 touches
3 conflicts

0x0f94ee4c…1899

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x0711ec2d…d973

0x34b655…2a6f

6 touches
3 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

10 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity