← previous blocknext block →recent activity

Analyzing

Block #74,360,954

11 transactions · 10 stateful · 2026-05-13 16:58:43 UTC

Parallelism

73/100

Blocked

40%

Avg conflicts / tx

0.55

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,360,954  ·  11 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

0x47b807a2…3307

0x065c9d…c394

6 touches
3 conflicts

0x61cb3937…e836

0x065c9d…c394

6 touches
3 conflicts

0x75799894…c9f4

0x065c9d…c394

4 touches
1 conflict

0xee5cee17…ad5b

0x065c9d…c394

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001a

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

3 conflicts on slot 0x47b807a243…c53307

← previous block·next block →recent activity