Block #71,627,840

← previous blocknext block →recent activity

Analyzing

Block #71,627,840

24 transactions · 20 stateful · 2026-05-01 01:18:03 UTC

Parallelism

83/100

Blocked

40%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #71,627,840  ·  24 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

0x676f9f01…a8ac

0x34b655…2a6f

8 touches
6 conflicts

0x08943ea2…ed03

0x754704…b603

6 touches
3 conflicts

0x005fb969…2d97

0x34b655…2a6f

4 touches
1 conflict

0x01e9f543…cb82

0x34b655…2a6f

4 touches
1 conflict

0x0520da1d…c88e

0x34b655…2a6f

4 touches
1 conflict

0x23114fac…630a

0x34b655…2a6f

4 touches
1 conflict

0x3702b140…97ea

0x34b655…2a6f

4 touches
1 conflict

0x408e66bb…3d6b

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

6 conflicts on slot 0x676f9f01ee…dea8ac

← previous block·next block →recent activity