← previous blocknext block →recent activity

Analyzing

Block #74,360,892

21 transactions · 14 stateful · 2026-05-13 16:58:18 UTC

Parallelism

76/100

Blocked

50%

Avg conflicts / tx

0.67

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,360,892  ·  21 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x8c49c85c…ee96

0x34b655…2a6f

10 touches
10 conflicts

0x433e2a5b…638d

0x34b655…2a6f

6 touches
3 conflicts

0x97d5efed…1aa4

0x34b655…2a6f

6 touches
3 conflicts

0xfe3d37ee…6e67

0x34b655…2a6f

6 touches
3 conflicts

0x3d096e0e…18bc

0xd32edf…ff58

5 touches
3 conflicts

0xcb45d9d6…cb82

0x1b6862…e19c

4 touches
1 conflict

0x0520da1d…c88e

0x34b655…2a6f

4 touches
1 conflict

0x17e2d2a0…359e

0x34b655…2a6f

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

10 conflicts on slot 0x8c49c85c3e…afee96

← previous block·next block →recent activity