← previous blocknext block →recent activity

Analyzing

Block #71,422,828

16 transactions · 15 stateful · 2026-04-30 02:28:55 UTC

Parallelism

75/100

Blocked

33%

Avg conflicts / tx

0.56

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #71,422,828  ·  16 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xc1f6cb7e…236c

0xd32edf…ff58

7 touches
6 conflicts

0x0eac6378…36f4

0x34b655…2a6f

4 touches
1 conflict

0x150af51d…9c42

0x34b655…2a6f

4 touches
1 conflict

0x15698ac9…2a46

0x34b655…2a6f

4 touches
1 conflict

0x21d22421…0b7a

0x34b655…2a6f

4 touches
1 conflict

0x3a9149df…72e0

0x34b655…2a6f

4 touches
1 conflict

0x3b74ae43…a235

0x34b655…2a6f

4 touches
1 conflict

0x3c35979a…975d

0x34b655…2a6f

4 touches
1 conflict

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

6 conflicts on slot 0xc1f6cb7e76…15236c

← previous block·next block →recent activity