← previous blocknext block →recent activity

Analyzing

Block #71,090,645

32 transactions · 25 stateful · 2026-04-28 13:36:28 UTC

Parallelism

78/100

Blocked

52%

Avg conflicts / tx

1

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #71,090,645  ·  32 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

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0x00000000…0002

0xb857c1…9be1

8 touches
6 conflicts

0x1630ed91…9774

0x34b655…2a6f

6 touches
3 conflicts

0x4ab14837…e1b2

0x2a68ba…90c5

4 touches
1 conflict

0x92d610a6…9a40

0x2a68ba…90c5

4 touches
1 conflict

0x3eadb0b6…d2f7

0x34b655…2a6f

4 touches
1 conflict

0x63b285f3…87ee

0x34b655…2a6f

4 touches
1 conflict

0x75f928fc…0465

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: 0x34b6552d…112a6f

21 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity