Block #71,092,286

← previous blocknext block →recent activity

Analyzing

Block #71,092,286

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

Parallelism

69/100

Blocked

44%

Avg conflicts / tx

0.94

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #71,092,286  ·  16 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

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x00000000…0002

0xb857c1…9be1

6 touches
3 conflicts

0x41755291…977f

0x131a2e…0da9

4 touches
1 conflict

0x11ff872c…bea1

0x065c9d…c394

3 touches
1 conflict

0x1b015a19…346e

0x065c9d…c394

3 touches
1 conflict

0x68a34e4b…8e59

0x73ada1…8be0

2 touches
0 conflicts

0x73863fc4…7d51

0x73ada1…8be0

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: 0x2a68ba18…8e90c5

6 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity