Block #71,172,132

← previous blocknext block →recent activity

Analyzing

Block #71,172,132

12 transactions · 9 stateful · 2026-04-28 22:39:12 UTC

Parallelism

83/100

Blocked

11%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,172,132  ·  12 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xebe62504…0f07

0x065c9d…c394

4 touches
1 conflict

0xf6ba9b21…5532

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0x2a37152b…a7c5

0x065c9d…c394

4 touches
1 conflict

0xcf1e7466…73e3

0x065c9d…c394

4 touches
1 conflict

0x636b5a56…794c

0x065c9d…c394

2 touches
1 conflict

0x67c8f5af…f9ce

0x065c9d…c394

2 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: 0x065c9d28…a9c394

1 conflict on slot 0xebe6250490…860f07

← previous block·next block →recent activity