← previous blocknext block →recent activity

Analyzing

Block #74,260,044

10 transactions · 9 stateful · 2026-05-13 05:47:31 UTC

Parallelism

70/100

Blocked

33%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,260,044  ·  10 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

0xb9d2cf20…a668

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xfe3b9476…2e67

0x34b655…2a6f

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x1031ac89…21db

0x065c9d…c394

2 touches
0 conflicts

0x22f59410…a606

0x065c9d…c394

2 touches
0 conflicts

0x27fe9236…66ba

0x065c9d…c394

2 touches
0 conflicts

0x3aa9fdc7…34f7

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: 0x34b6552d…112a6f

3 conflicts on slot 0xb9d2cf2005…28a668

← previous block·next block →recent activity