← previous blocknext block →recent activity

Analyzing

Block #74,237,612

7 transactions · 6 stateful · 2026-05-13 03:18:28 UTC

Parallelism

57/100

Blocked

33%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,237,612  ·  7 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

0x768cffcd…2648

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x0520da1d…c88e

0x34b655…2a6f

2 touches
0 conflicts

0x2965e2d6…5800

0x34b655…2a6f

2 touches
0 conflicts

0x3817764d…242b

0x34b655…2a6f

2 touches
0 conflicts

0x4858af56…10ef

0x34b655…2a6f

2 touches
0 conflicts

0x56a064ab…6c7d

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 0x768cffcdb0…d12648

← previous block·next block →recent activity