← previous blocknext block →recent activity

Analyzing

Block #71,176,534

9 transactions · 9 stateful · 2026-04-28 23:08:33 UTC

Parallelism

78/100

Blocked

11%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,176,534  ·  9 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

0xf9d262f1…5850

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0624466c…833e

0x065c9d…c394

4 touches
1 conflict

0x083ad6a1…6b04

0x065c9d…c394

4 touches
1 conflict

0x1ca7e5d9…3b12

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0xbb6b5cc3…4c49

0x103222…7496

2 touches
0 conflicts

0xd9aa4f05…b66a

0x68b507…ec44

2 touches
0 conflicts

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: 0x065c9d28…a9c394

1 conflict on slot 0xf9d262f1b9…085850

← previous block·next block →recent activity