← previous blocknext block →recent activity

Analyzing

Block #71,090,633

16 transactions · 15 stateful · 2026-04-28 13:36:23 UTC

Parallelism

44/100

Blocked

53%

Avg conflicts / tx

2.13

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #71,090,633  ·  16 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

16 touches
28 conflicts

0x41755291…977f

0x131a2e…0da9

8 touches
6 conflicts

0x41755291…977f

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x131a2e…0da9

6 touches
3 conflicts

0xf19fcf64…6521

0x065c9d…c394

3 touches
1 conflict

0x4cb2b152…2e00

0x131a2e…0da9

2 touches
0 conflicts

0x4ab14837…e1b2

0x2a68ba…90c5

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

28 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity