Block #71,448,391

← previous blocknext block →recent activity

Analyzing

Block #71,448,391

10 transactions · 10 stateful · 2026-04-30 05:19:16 UTC

Parallelism

70/100

Blocked

20%

Avg conflicts / tx

0.3

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #71,448,391  ·  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

0x5f77d607…2c84

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x2a84ca97…4adc

0x065c9d…c394

2 touches
0 conflicts

0xa74946bc…bb67

0x065c9d…c394

2 touches
0 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

2 touches
0 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

2 touches
0 conflicts

0x085df2c1…305a

0x34b655…2a6f

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 0x5f77d60791…b12c84

← previous block·next block →recent activity