← previous blocknext block →recent activity

Analyzing

Block #71,176,427

14 transactions · 12 stateful · 2026-04-28 23:07:50 UTC

Parallelism

71/100

Blocked

42%

Avg conflicts / tx

0.57

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #71,176,427  ·  14 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

0x8c49c85c…ee96

0x34b655…2a6f

6 touches
3 conflicts

0xe72e3a59…9a0f

0x065c9d…c394

5 touches
3 conflicts

0x3d2f95f3…4559

0xd32edf…ff58

5 touches
3 conflicts

0xf35dca9e…bd8a

0x1b6862…e19c

4 touches
1 conflict

0xc3c8642a…7da5

0x2a68ba…90c5

4 touches
1 conflict

0x148e0217…34a2

0x34b655…2a6f

4 touches
1 conflict

0x1e9fccc4…5c21

0x34b655…2a6f

4 touches
1 conflict

0x414e9446…4b59

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

3 conflicts on slot 0x8c49c85c3e…afee96

← previous block·next block →recent activity