Block #71,239,380

← previous blocknext block →recent activity

Analyzing

Block #71,239,380

16 transactions · 14 stateful · 2026-04-29 06:06:32 UTC

Parallelism

69/100

Blocked

43%

Avg conflicts / tx

0.75

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #71,239,380  ·  16 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0x7ee110ef…8394

0x34b655…2a6f

8 touches
6 conflicts

0x613f945f…b850

0x34b655…2a6f

6 touches
3 conflicts

0xb1dcb4b3…4b74

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x7cb2f3fa…4836

0x34b655…2a6f

4 touches
1 conflict

0x893cd52c…5766

0x34b655…2a6f

4 touches
1 conflict

0x8992f474…0529

0x34b655…2a6f

4 touches
1 conflict

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

6 conflicts on slot 0xac2a02739b…81721b

← previous block·next block →recent activity