← previous blocknext block →recent activity

Analyzing

Block #74,346,688

14 transactions · 12 stateful · 2026-05-13 15:23:53 UTC

Parallelism

79/100

Blocked

42%

Avg conflicts / tx

0.5

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,346,688  ·  14 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

0x262bb27b…6b2c

0x11ed3b…2c96

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x0711ec2d…d973

0x34b655…2a6f

4 touches
1 conflict

0x1b9e654e…0a08

0x34b655…2a6f

4 touches
1 conflict

0x313f2565…5b00

0x34b655…2a6f

4 touches
1 conflict

0x36f4b4f0…0188

0x34b655…2a6f

4 touches
1 conflict

0x4f483049…3cc7

0x34b655…2a6f

4 touches
1 conflict

0xc6417de0…2191

0xc8689a…ee79

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: 0x11ed3b12…842c96

3 conflicts on slot 0x262bb27bbd…f06b2c

← previous block·next block →recent activity