← previous blocknext block →recent activity

Analyzing

Block #71,622,297

8 transactions · 8 stateful · 2026-05-01 00:41:08 UTC

Parallelism

75/100

Blocked

13%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,622,297  ·  8 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

0x08d31c28…d50f

0x34b655…2a6f

4 touches
1 conflict

0x1674d3d4…275f

0x34b655…2a6f

4 touches
1 conflict

0x676f9f01…a8ac

0x34b655…2a6f

4 touches
1 conflict

0xb9868b52…c77f

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x443a3e47…f4a4

0x065c9d…c394

2 touches
0 conflicts

0x53271776…6e90

0x065c9d…c394

2 touches
0 conflicts

0x797bdc6a…8ed3

0x065c9d…c394

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: 0x34b6552d…112a6f

1 conflict on slot 0x08d31c2849…fed50f

← previous block·next block →recent activity