← previous blocknext block →recent activity

Analyzing

Block #71,422,794

11 transactions · 10 stateful · 2026-04-30 02:28:41 UTC

Parallelism

28/100

Blocked

70%

Avg conflicts / tx

2.55

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #71,422,794  ·  11 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

0xa472d565…9fe4

0x3bd359…433a

16 touches
28 conflicts

0x00000000…0000

0x7d0364…a52b

14 touches
21 conflicts

0x00000000…0001

0x7d0364…a52b

14 touches
21 conflicts

0x131ec7f4…baaf

0xaca864…7777

14 touches
21 conflicts

0x44ad89ba…cf83

0xaca864…7777

14 touches
21 conflicts

0xaadf42dc…f433

0x3bd359…433a

14 touches
21 conflicts

0x551f6273…7c20

0x42a4aa…7777

2 touches
0 conflicts

0x09106a95…1467

0xeedfbc…f7dc

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: 0x3bd359c1…15433a

28 conflicts on slot 0xa472d565a0…ae9fe4

← previous block·next block →recent activity