← previous blocknext block →recent activity

Analyzing

Block #71,696,424

10 transactions · 10 stateful · 2026-05-01 08:54:36 UTC

Parallelism

70/100

Blocked

20%

Avg conflicts / tx

0.2

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #71,696,424  ·  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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xfb1f1167…3da4

0x065c9d…c394

4 touches
1 conflict

0x82f49ab9…6fb1

0xd32edf…ff58

3 touches
1 conflict

0x422689c2…1ab8

0x065c9d…c394

3 touches
1 conflict

0x4e1daa73…d0a6

0x065c9d…c394

3 touches
1 conflict

0x144eb617…4143

0x065c9d…c394

2 touches
0 conflicts

0x32c48a7e…5028

0x065c9d…c394

2 touches
0 conflicts

0xd74d5bed…5e7e

0x2a68ba…90c5

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 0x0000000000…00003d

← previous block·next block →recent activity