Block #71,042,219

← previous blocknext block →recent activity

Analyzing

Block #71,042,219

15 transactions · 13 stateful · 2026-04-28 08:13:53 UTC

Parallelism

80/100

Blocked

38%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #71,042,219  ·  15 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

0x92d610a6…9a40

0x2a68ba…90c5

6 touches
3 conflicts

0x422394ab…0300

0x065c9d…c394

5 touches
3 conflicts

0x6af306bb…2e81

0x3bd359…433a

4 touches
1 conflict

0x1c354dc0…96de

0x754704…b603

4 touches
1 conflict

0x943bf267…fd17

0x754704…b603

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0xf91b744e…9117

0x754704…b603

4 touches
1 conflict

0x60f7fbaf…bd58

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: 0x2a68ba18…8e90c5

3 conflicts on slot 0x92d610a6f9…379a40

← previous block·next block →recent activity