← previous blocknext block →recent activity

Analyzing

Block #74,328,777

13 transactions · 10 stateful · 2026-05-13 13:24:45 UTC

Parallelism

85/100

Blocked

10%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,328,777  ·  13 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x4f3a6b4a…3819

0x34b655…2a6f

4 touches
1 conflict

0xf3477df9…dcdb

0x34b655…2a6f

4 touches
1 conflict

0xa9988419…9f45

0x34b655…2a6f

4 touches
1 conflict

0x0c1aa307…ff9c

0x34b655…2a6f

2 touches
0 conflicts

0x310a7246…2dcb

0x34b655…2a6f

2 touches
0 conflicts

0x482471ad…122f

0x34b655…2a6f

2 touches
0 conflicts

0x51087f5a…61f7

0x34b655…2a6f

2 touches
0 conflicts

0x5e1c23e9…4f81

0x34b655…2a6f

2 touches
0 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

1 conflict on slot 0x4f3a6b4a49…e93819

← previous block·next block →recent activity