Block #71,177,195

← previous blocknext block →recent activity

Analyzing

Block #71,177,195

20 transactions · 18 stateful · 2026-04-28 23:12:53 UTC

Parallelism

75/100

Blocked

39%

Avg conflicts / tx

0.5

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #71,177,195  ·  20 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x8c49c85c…ee96

0x34b655…2a6f

6 touches
3 conflicts

0xc684c7fc…0547

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x10c8e8fe…d4fd

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…0002

0xb857c1…9be1

4 touches
1 conflict

0x043fd7a0…bb94

0x34b655…2a6f

4 touches
1 conflict

0x148e0217…34a2

0x34b655…2a6f

4 touches
1 conflict

0x284309a8…f4be

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

3 conflicts on slot 0x8c49c85c3e…afee96

← previous block·next block →recent activity