Block #71,555,879

← previous blocknext block →recent activity

Analyzing

Block #71,555,879

8 transactions · 8 stateful · 2026-04-30 17:19:04 UTC

Parallelism

50/100

Blocked

38%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #71,555,879  ·  8 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x676f9f01…a8ac

0x34b655…2a6f

6 touches
3 conflicts

0xb9868b52…c77f

0x34b655…2a6f

6 touches
3 conflicts

0x0eac6378…36f4

0x34b655…2a6f

4 touches
1 conflict

0x150af51d…9c42

0x34b655…2a6f

4 touches
1 conflict

0x3254d19b…f714

0x34b655…2a6f

4 touches
1 conflict

0x3c35979a…975d

0x34b655…2a6f

4 touches
1 conflict

0x143dba04…1b98

0x8d66a4…3095

4 touches
1 conflict

0x1e451306…7993

0x8d66a4…3095

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

3 conflicts on slot 0x676f9f01ee…dea8ac

← previous block·next block →recent activity