Block #71,643,036

← previous blocknext block →recent activity

Analyzing

Block #71,643,036

19 transactions · 15 stateful · 2026-05-01 02:59:09 UTC

Parallelism

63/100

Blocked

40%

Avg conflicts / tx

1.11

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #71,643,036  ·  19 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

0xa21e8abe…a7f1

0x34b655…2a6f

6 touches
3 conflicts

0xf6d214b0…8abe

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xee0b2bd0…28d5

0x34b655…2a6f

4 touches
2 conflicts

0xf8f1e808…a4fd

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x664bf99e…0a8c

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