← previous blocknext block →recent activity

Analyzing

Block #71,743,660

20 transactions · 17 stateful · 2026-05-01 14:09:08 UTC

Parallelism

60/100

Blocked

53%

Avg conflicts / tx

1.5

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #71,743,660  ·  20 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

0x00000000…0002

0x7e9d3a…9fda

16 touches
28 conflicts

0xf3b12578…d997

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x0d83c0ff…7e40

0x065c9d…c394

4 touches
1 conflict

0xa3616b13…6c9a

0x065c9d…c394

3 touches
1 conflict

0x26dc8876…ab41

0x065c9d…c394

3 touches
1 conflict

0x2d7c6d68…b14c

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: 0x7e9d3a8a…4f9fda

28 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity