← previous blocknext block →recent activity

Analyzing

Block #74,767,607

16 transactions · 15 stateful · 2026-05-15 14:16:02 UTC

Parallelism

63/100

Blocked

53%

Avg conflicts / tx

1.13

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,767,607  ·  16 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

12 touches
15 conflicts

0x9cc607d0…c9c7

0x34b655…2a6f

8 touches
6 conflicts

0x6eba5e7f…4b52

0x34b655…2a6f

8 touches
6 conflicts

0xc6417de0…2191

0xc8689a…ee79

8 touches
6 conflicts

0x313f2565…5b00

0x34b655…2a6f

8 touches
6 conflicts

0x388e001a…7e04

0x34b655…2a6f

8 touches
6 conflicts

0x8db1e0f2…2fcf

0x34b655…2a6f

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: Perpl

15 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity