← previous blocknext block →recent activity

Analyzing

Block #74,308,843

7 transactions · 6 stateful · 2026-05-13 11:12:10 UTC

Parallelism

71/100

Blocked

17%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,308,843  ·  7 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

0x24968e6d…0132

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x4ad4589b…27b8

0x065c9d…c394

2 touches
0 conflicts

0x556d9ba7…f8a1

0x065c9d…c394

2 touches
0 conflicts

0x6a19eda1…93c2

0x065c9d…c394

2 touches
0 conflicts

0x87a07bb4…2b41

0x065c9d…c394

2 touches
0 conflicts

0x96eb6452…948b

0x065c9d…c394

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

1 conflict on slot 0x24968e6db4…f00132

← previous block·next block →recent activity