← previous blocknext block →recent activity

Analyzing

Block #74,482,402

19 transactions · 10 stateful · 2026-05-14 06:27:06 UTC

Parallelism

84/100

Blocked

20%

Avg conflicts / tx

0.16

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,482,402  ·  19 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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xd29b6af0…75ee

0x065c9d…c394

4 touches
1 conflict

0x5d5740ff…14d1

0x065c9d…c394

4 touches
1 conflict

0xb00ff82e…2ec2

0x065c9d…c394

2 touches
0 conflicts

0xffe431af…8faa

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0013

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0015

0x1b6862…e19c

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity