← previous blocknext block →recent activity

Analyzing

Block #71,741,126

40 transactions · 22 stateful · 2026-05-01 13:52:13 UTC

Parallelism

75/100

Blocked

55%

Avg conflicts / tx

1.2

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #71,741,126  ·  40 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0xb2c47936…bb26

0xd32edf…ff58

19 touches
45 conflicts

0xba5743c7…21c4

0x1b6862…e19c

4 touches
1 conflict

0xf6cc7de8…0b4a

0x3bd359…433a

4 touches
1 conflict

0x00000000…0000

0x63e48b…53f2

4 touches
1 conflict

0x00000000…0003

0x63e48b…53f2

4 touches
1 conflict

0x00000000…0004

0x63e48b…53f2

4 touches
1 conflict

0x9a555477…19a8

0x754704…b603

4 touches
1 conflict

0x00000000…0002

0x7e9d3a…9fda

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: 0xd32edf66…9fff58

45 conflicts on slot 0xb2c479360a…7fbb26

← previous block·next block →recent activity