Block #71,092,243

← previous blocknext block →recent activity

Analyzing

Block #71,092,243

28 transactions · 25 stateful · 2026-04-28 13:47:08 UTC

Parallelism

82/100

Blocked

36%

Avg conflicts / tx

0.57

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #71,092,243  ·  28 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

0x195bd06d…0220

0xd32edf…ff58

9 touches
10 conflicts

0x0d0b2509…074d

0x3bd359…433a

6 touches
3 conflicts

0xe6455d1f…1029

0x754704…b603

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1539

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0000

0x8fd63a…536c

4 touches
1 conflict

0x00000000…0001

0x8fd63a…536c

4 touches
1 conflict

0x00000000…0005

0x2a3755…a5a6

2 touches
0 conflicts

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

10 conflicts on slot 0x195bd06d9d…870220

← previous block·next block →recent activity