← previous blocknext block →recent activity

Analyzing

Block #71,701,017

26 transactions · 20 stateful · 2026-05-01 09:25:05 UTC

Parallelism

69/100

Blocked

45%

Avg conflicts / tx

1.35

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #71,701,017  ·  26 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xdc6d60a2…d90b

0xd32edf…ff58

15 touches
28 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

8 touches
6 conflicts

0x711e7e56…1a2b

0x065c9d…c394

7 touches
6 conflicts

0xd2885b51…39cf

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x7f571e09…a35f

0x065c9d…c394

3 touches
1 conflict

0xd050ebb6…7ad4

0x065c9d…c394

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

28 conflicts on slot 0xdc6d60a289…e8d90b

← previous block·next block →recent activity