← previous blocknext block →recent activity

Analyzing

Block #71,092,162

26 transactions · 21 stateful · 2026-04-28 13:46:35 UTC

Parallelism

88/100

Blocked

14%

Avg conflicts / tx

0.15

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #71,092,162  ·  26 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x86d76bea…40b4

0xd32edf…ff58

5 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x18aed20c…48f3

0x000000…012a

2 touches
0 conflicts

0x335a161d…fe7f

0x000000…012a

2 touches
0 conflicts

0x1784d827…0b0e

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0013

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0015

0x1b6862…e19c

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

3 conflicts on slot 0x86d76beaba…6040b4

← previous block·next block →recent activity