← previous blocknext block →recent activity

Analyzing

Block #71,417,789

13 transactions · 11 stateful · 2026-04-30 01:55:20 UTC

Parallelism

85/100

Blocked

18%

Avg conflicts / tx

0.15

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,417,789  ·  13 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

0x01e7b865…6e6d

0x188d58…ea8e

4 touches
1 conflict

0x01e7b865…6e6e

0x188d58…ea8e

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0xfcb7b8b2…ebb3

0x065c9d…c394

4 touches
1 conflict

0x53d15633…67d7

0x065c9d…c394

3 touches
1 conflict

0x5b109150…3856

0x065c9d…c394

3 touches
1 conflict

0x92d610a6…9a40

0x2a68ba…90c5

2 touches
0 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

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: 0x188d586d…f9ea8e

1 conflict on slot 0x01e7b86585…4d6e6d

← previous block·next block →recent activity