Block #71,042,121

← previous blocknext block →recent activity

Analyzing

Block #71,042,121

7 transactions · 6 stateful · 2026-04-28 08:13:14 UTC

Parallelism

71/100

Blocked

17%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

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

0x005fb969…2d97

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x462c8be7…4f83

0x8d66a4…3095

3 touches
1 conflict

0x5ba51e87…44ee

0x8d66a4…3095

3 touches
1 conflict

0x8a35acfb…d1ae

0x8d66a4…3095

3 touches
1 conflict

0x8a35acfb…d1af

0x8d66a4…3095

3 touches
1 conflict

0x8a35acfb…d1b0

0x8d66a4…3095

3 touches
1 conflict

0x96504a63…52d2

0x8d66a4…3095

3 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 0x005fb969d5…0c2d97

← previous block·next block →recent activity