← previous blocknext block →recent activity

Analyzing

Block #74,331,831

19 transactions · 14 stateful · 2026-05-13 13:45:03 UTC

Parallelism

79/100

Blocked

36%

Avg conflicts / tx

0.37

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,331,831  ·  19 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xb409e204…89ac

0x34b655…2a6f

4 touches
1 conflict

0x6a53b1c0…c3f2

0x34b655…2a6f

4 touches
1 conflict

0x5ba4db2b…2f04

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0019

0x1b6862…e19c

4 touches
1 conflict

0xcb45d9d6…cb81

0x1b6862…e19c

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: 0x34b6552d…112a6f

3 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity