← previous blocknext block →recent activity

Analyzing

Block #71,743,446

13 transactions · 13 stateful · 2026-05-01 14:07:42 UTC

Parallelism

62/100

Blocked

31%

Avg conflicts / tx

0.77

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #71,743,446  ·  13 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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xeebd31ac…0794

0x34b655…2a6f

6 touches
3 conflicts

0xfb790f01…fea9

0x34b655…2a6f

6 touches
3 conflicts

0x463be44a…2830

0x34b655…2a6f

4 touches
1 conflict

0x64461c10…e86d

0x34b655…2a6f

4 touches
1 conflict

0xc166a323…1f33

0x34b655…2a6f

3 touches
1 conflict

0x01737532…9b12

0x34b655…2a6f

3 touches
1 conflict

0xd6aabe89…92f5

0x34b655…2a6f

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

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity