Block #71,557,696

← previous blocknext block →recent activity

Analyzing

Block #71,557,696

15 transactions · 11 stateful · 2026-04-30 17:31:10 UTC

Parallelism

87/100

Blocked

9%

Avg conflicts / tx

0.07

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

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

0xc6d2c861…9c7c

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x443a3e47…f4a4

0x065c9d…c394

2 touches
0 conflicts

0x5c5da86c…7424

0x065c9d…c394

2 touches
0 conflicts

0x80f1fbe3…f6f5

0x065c9d…c394

2 touches
0 conflicts

0xfcb7b8b2…ebb3

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

1 conflict on slot 0xc6d2c86117…4b9c7c

← previous block·next block →recent activity