← previous blocknext block →recent activity

Analyzing

Block #71,070,788

16 transactions · 15 stateful · 2026-04-28 11:24:09 UTC

Parallelism

88/100

Blocked

7%

Avg conflicts / tx

0.06

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,070,788  ·  16 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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0xe3824882…dc68

0x065c9d…c394

3 touches
1 conflict

0x8f701ab6…fd74

0x065c9d…c394

3 touches
1 conflict

0x18aed20c…48f3

0x000000…012a

2 touches
0 conflicts

0x4245e4e8…096e

0x000000…012a

2 touches
0 conflicts

0x7b43f938…3650

0x000000…012a

2 touches
0 conflicts

0x01e7b865…6e6d

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: 0x065c9d28…a9c394

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity