← previous blocknext block →recent activity

Analyzing

Block #74,215,443

10 transactions · 7 stateful · 2026-05-13 00:51:03 UTC

Parallelism

80/100

Blocked

14%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,215,443  ·  10 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

0x310a7246…2dcb

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x99db93cc…d61f

0x34b655…2a6f

3 touches
1 conflict

0x687ae1ea…4160

0x065c9d…c394

2 touches
0 conflicts

0x17d87f0d…bfc5

0x34b655…2a6f

2 touches
0 conflicts

0x3dda6fbb…e784

0x34b655…2a6f

2 touches
0 conflicts

0x482471ad…122f

0x34b655…2a6f

2 touches
0 conflicts

0x4ec9ff52…e6f7

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 0x310a7246ab…012dcb

← previous block·next block →recent activity