Block #71,446,284

← previous blocknext block →recent activity

Analyzing

Block #71,446,284

8 transactions · 8 stateful · 2026-04-30 05:05:14 UTC

Parallelism

63/100

Blocked

25%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #71,446,284  ·  8 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

0xb38a28f3…0ca9

0x065c9d…c394

5 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0xc3c8642a…7da5

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x032ce57f…eb27

0x065c9d…c394

2 touches
0 conflicts

0x24e7c521…00a9

0x065c9d…c394

2 touches
0 conflicts

0x5c007b31…1514

0x065c9d…c394

2 touches
0 conflicts

0x8e50b1ad…7101

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

3 conflicts on slot 0xb38a28f3b6…4e0ca9

← previous block·next block →recent activity