← previous blocknext block →recent activity

Analyzing

Block #74,456,691

23 transactions · 17 stateful · 2026-05-14 03:36:05 UTC

Parallelism

87/100

Blocked

47%

Avg conflicts / tx

0.48

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,456,691  ·  23 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

0xf3981be5…2c47

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0002

0xab3526…fa38

6 touches
3 conflicts

0xae2e2e10…4b15

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…001c

0x1b6862…e19c

4 touches
1 conflict

0xffe431af…8faa

0x065c9d…c394

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002c

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 0xf3981be56e…f02c47

← previous block·next block →recent activity