← previous blocknext block →recent activity

Analyzing

Block #71,450,749

23 transactions · 21 stateful · 2026-04-30 05:34:59 UTC

Parallelism

70/100

Blocked

71%

Avg conflicts / tx

1.35

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #71,450,749  ·  23 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x0dbf9688…c6cf

0xd18b7e…414b

8 touches
6 conflicts

0x8a35acfb…d1ad

0x8d66a4…3095

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xf26eda05…0203

0xd18b7e…414b

6 touches
3 conflicts

0x1c354dc0…96de

0x754704…b603

6 touches
3 conflicts

0xf91b744e…9117

0x754704…b603

6 touches
3 conflicts

0x109d8a52…a7b7

0x34b655…2a6f

6 touches
3 conflicts

0x17ce7874…0569

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: 0xd18b7ec5…10414b

6 conflicts on slot 0x0dbf9688de…b0c6cf

← previous block·next block →recent activity