← previous blocknext block →recent activity

Analyzing

Block #71,238,826

11 transactions · 11 stateful · 2026-04-29 06:02:51 UTC

Parallelism

55/100

Blocked

36%

Avg conflicts / tx

0.55

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #71,238,826  ·  11 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x157b6348…8604

0x34b655…2a6f

4 touches
1 conflict

0xe96c91d2…32ff

0x8d66a4…3095

4 touches
1 conflict

0x01737532…9b12

0x34b655…2a6f

4 touches
1 conflict

0xf8f1e808…a4fd

0x34b655…2a6f

4 touches
1 conflict

0x468c69b1…af11

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1ac

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 0xac2a02739b…81721b

← previous block·next block →recent activity