Block #71,417,345

← previous blocknext block →recent activity

Analyzing

Block #71,417,345

10 transactions · 8 stateful · 2026-04-30 01:52:24 UTC

Parallelism

80/100

Blocked

13%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,417,345  ·  10 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

0xa25f60e7…0bfc

0x065c9d…c394

4 touches
1 conflict

0xd9f4b00b…3de2

0x065c9d…c394

3 touches
1 conflict

0x698bd3ce…9949

0x065c9d…c394

3 touches
1 conflict

0x1332f531…e649

0x34b655…2a6f

2 touches
0 conflicts

0x14046d6a…bc5e

0x34b655…2a6f

2 touches
0 conflicts

0x232df012…c608

0x34b655…2a6f

2 touches
0 conflicts

0x51087f5a…61f7

0x34b655…2a6f

2 touches
0 conflicts

0x60f7fbaf…bd58

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

1 conflict on slot 0xa25f60e76f…a10bfc

← previous block·next block →recent activity