Block #71,708,840

← previous blocknext block →recent activity

Analyzing

Block #71,708,840

9 transactions · 9 stateful · 2026-05-01 10:17:08 UTC

Parallelism

67/100

Blocked

22%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #71,708,840  ·  9 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x1b5d2e60…99b5

0x34b655…2a6f

4 touches
1 conflict

0x801a6e57…d85c

0x34b655…2a6f

4 touches
1 conflict

0x9e719c7a…df63

0x34b655…2a6f

4 touches
1 conflict

0xd2b8cc8b…85fa

0x34b655…2a6f

4 touches
1 conflict

0xfae08fbb…e8a0

0x34b655…2a6f

4 touches
1 conflict

0x7da6aef8…0899

0x065c9d…c394

2 touches
0 conflicts

0xac396ef5…4953

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity