← previous blocknext block →recent activity

Analyzing

Block #71,283,926

17 transactions · 14 stateful · 2026-04-29 11:03:01 UTC

Parallelism

59/100

Blocked

57%

Avg conflicts / tx

1.35

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #71,283,926  ·  17 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

0x7170c140…36bc

0x34b655…2a6f

6 touches
3 conflicts

0x388f889f…a655

0x34b655…2a6f

6 touches
3 conflicts

0xb96e29a5…0419

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…001c

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002c

0x1b6862…e19c

4 touches
1 conflict

0xc3483764…f29a

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

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