← previous blocknext block →recent activity

Analyzing

Block #74,918,682

16 transactions · 12 stateful · 2026-05-16 07:03:58 UTC

Parallelism

88/100

Blocked

33%

Avg conflicts / tx

0.25

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,918,682  ·  16 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xdbc6e634…e16a

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0x00000000…0000

0x80c3ba…cd70

4 touches
1 conflict

0xe3437414…3948

0x065c9d…c394

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x3e49348b…9445

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: 0x1b68626d…2de19c

1 conflict on slot 0xdbc6e63468…c6e16a

← previous block·next block →recent activity