← previous blocknext block →recent activity

Analyzing

Block #71,042,725

6 transactions · 6 stateful · 2026-04-28 08:17:15 UTC

Parallelism

67/100

Blocked

17%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,042,725  ·  6 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

0xfefb0189…f726

0x34b655…2a6f

4 touches
1 conflict

0x09000000…0007

0x000000…1000

2 touches
0 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x3625ca65…6f73

0x065c9d…c394

2 touches
0 conflicts

0x51ecdf19…e365

0x065c9d…c394

2 touches
0 conflicts

0x66a51112…6aa3

0x065c9d…c394

2 touches
0 conflicts

0xd307e808…bc34

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 0xfefb01895a…9bf726

← previous block·next block →recent activity