← previous blocknext block →recent activity

Analyzing

Block #74,606,243

9 transactions · 9 stateful · 2026-05-14 20:19:00 UTC

Parallelism

67/100

Blocked

33%

Avg conflicts / tx

0.44

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,606,243  ·  9 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

0x4ec9ff52…e6f7

0x34b655…2a6f

6 touches
3 conflicts

0xa10c86f8…4b74

0x3bd359…433a

4 touches
1 conflict

0x00000000…0000

0x019883…2a9a

4 touches
1 conflict

0x00000000…0002

0x019883…2a9a

4 touches
1 conflict

0x44ad89ba…cf83

0x0cc9b2…7777

4 touches
1 conflict

0x99a3a7c1…1e2b

0x0cc9b2…7777

4 touches
1 conflict

0xa472d565…9fe4

0x3bd359…433a

4 touches
1 conflict

0x00000000…0002

0xab3526…fa38

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

3 conflicts on slot 0x4ec9ff52ce…67e6f7

← previous block·next block →recent activity