← previous blocknext block →recent activity

Analyzing

Block #71,741,075

34 transactions · 31 stateful · 2026-05-01 13:51:52 UTC

Parallelism

79/100

Blocked

58%

Avg conflicts / tx

1.35

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #71,741,075  ·  34 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

0x00000000…0002

0x7e9d3a…9fda

14 touches
21 conflicts

0xffcb0f83…1519

0xd32edf…ff58

11 touches
15 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x63d7ebf0…3dd9

0x34b655…2a6f

6 touches
3 conflicts

0x1c389468…6b0e

0x34b655…2a6f

6 touches
3 conflicts

0xf3981be5…2c47

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0004

0x63e48b…53f2

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: 0x7e9d3a8a…4f9fda

21 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity