← previous blocknext block →recent activity

Analyzing

Block #71,701,014

13 transactions · 10 stateful · 2026-05-01 09:25:04 UTC

Parallelism

77/100

Blocked

30%

Avg conflicts / tx

0.23

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #71,701,014  ·  13 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xfadc118d…5d64

0x34b655…2a6f

4 touches
1 conflict

0x35c22577…08c5

0x065c9d…c394

3 touches
1 conflict

0x6658a42a…f35f

0xd32edf…ff58

3 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0015

0x1b6862…e19c

2 touches
0 conflicts

0x17ca7036…1e18

0x1b6862…e19c

2 touches
0 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

2 touches
0 conflicts

0x4bef88e0…eaca

0x3bd359…433a

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 0xfadc118dc2…025d64

← previous block·next block →recent activity