← previous blocknext block →recent activity

Analyzing

Block #71,090,561

16 transactions · 14 stateful · 2026-04-28 13:35:55 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,090,561  ·  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…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0xa4e3b3b1…0911

0x2a68ba…90c5

4 touches
1 conflict

0x75e73565…45f4

0x1b6862…e19c

4 touches
1 conflict

0x32512c1e…14fa

0xa6afd3…d132

3 touches
1 conflict

0xe02846c2…a5b6

0xd32edf…ff58

3 touches
1 conflict

0x00000000…0028

0x1b6862…e19c

2 touches
0 conflicts

0x09000000…0001

0x000000…1000

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: 0x1b68626d…2de19c

1 conflict on slot 0x0000000000…000013

← previous block·next block →recent activity