← previous blocknext block →recent activity

Analyzing

Block #71,092,164

34 transactions · 28 stateful · 2026-04-28 13:46:36 UTC

Parallelism

76/100

Blocked

54%

Avg conflicts / tx

1.59

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #71,092,164  ·  34 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xc286dc0e…4045

0xd32edf…ff58

15 touches
28 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0x2cf96c0a…538a

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0018

0x1b6862…e19c

6 touches
3 conflicts

0xcb45d9d6…cb80

0x1b6862…e19c

6 touches
3 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 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

28 conflicts on slot 0xc286dc0ee2…004045

← previous block·next block →recent activity