Block #71,416,696

← previous blocknext block →recent activity

Analyzing

Block #71,416,696

9 transactions · 7 stateful · 2026-04-30 01:48:05 UTC

Parallelism

78/100

Blocked

14%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

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

0x676f9f01…a8ac

0x34b655…2a6f

4 touches
1 conflict

0x8d77736d…38bb

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x1a894849…f653

0x065c9d…c394

2 touches
0 conflicts

0x45cecbba…71e8

0x065c9d…c394

2 touches
0 conflicts

0x9773774b…8d3f

0x065c9d…c394

2 touches
0 conflicts

0x9d6545b8…a685

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 0x676f9f01ee…dea8ac

← previous block·next block →recent activity