Block #71,701,503

← previous blocknext block →recent activity

Analyzing

Block #71,701,503

15 transactions · 13 stateful · 2026-05-01 09:28:20 UTC

Parallelism

87/100

Blocked

8%

Avg conflicts / tx

0.07

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,701,503  ·  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

0xfadc118d…5d64

0x34b655…2a6f

4 touches
1 conflict

0x2233f38c…0d84

0x34b655…2a6f

4 touches
1 conflict

0x433e2a5b…638d

0x34b655…2a6f

4 touches
1 conflict

0x4546ebad…b908

0x34b655…2a6f

4 touches
1 conflict

0x64a1d480…4092

0x34b655…2a6f

4 touches
1 conflict

0x8c49c85c…ee96

0x34b655…2a6f

4 touches
1 conflict

0xac206e47…ef7d

0x34b655…2a6f

4 touches
1 conflict

0xcbd23469…a4df

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

1 conflict on slot 0xfadc118dc2…025d64

← previous block·next block →recent activity