← previous blocknext block →recent activity

Analyzing

Block #71,648,455

20 transactions · 15 stateful · 2026-05-01 03:35:09 UTC

Parallelism

80/100

Blocked

27%

Avg conflicts / tx

0.35

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #71,648,455  ·  20 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

0x668e819b…e7eb

0xd32edf…ff58

7 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x92339d95…0800

0x0000a8…8888

2 touches
0 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

2 touches
0 conflicts

0x01e7b865…6e6f

0x188d58…ea8e

2 touches
0 conflicts

0xfbad2c6c…0d32

0x188d58…ea8e

2 touches
0 conflicts

0xfbad2c6c…0d34

0x188d58…ea8e

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: 0xd32edf66…9fff58

6 conflicts on slot 0x668e819b2f…31e7eb

← previous block·next block →recent activity