← previous blocknext block →recent activity

Analyzing

Block #74,565,886

14 transactions · 12 stateful · 2026-05-14 15:48:29 UTC

Parallelism

79/100

Blocked

33%

Avg conflicts / tx

0.36

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,565,886  ·  14 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

0x7facbeb5…e056

0x065c9d…c394

4 touches
1 conflict

0xc2aacf41…5503

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x24968e6d…0132

0x065c9d…c394

4 touches
1 conflict

0xbbee74c2…567a

0x065c9d…c394

4 touches
1 conflict

0x5f89ddfe…452c

0xd32edf…ff58

3 touches
1 conflict

0x954060de…bbe4

0x065c9d…c394

3 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: 0x065c9d28…a9c394

1 conflict on slot 0x7facbeb535…f6e056

← previous block·next block →recent activity