← previous blocknext block →recent activity

Analyzing

Block #71,070,815

24 transactions · 22 stateful · 2026-04-28 11:24:20 UTC

Parallelism

54/100

Blocked

50%

Avg conflicts / tx

2.33

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #71,070,815  ·  24 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0xb857c1…9be1

22 touches
55 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0xa3a30226…e369

0x065c9d…c394

3 touches
1 conflict

0x59fcabe2…631a

0x065c9d…c394

3 touches
1 conflict

0x00000000…0018

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: 0xb857c13a…1a9be1

55 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity