← previous blocknext block →recent activity

Analyzing

Block #71,069,960

40 transactions · 34 stateful · 2026-04-28 11:18:37 UTC

Parallelism

85/100

Blocked

50%

Avg conflicts / tx

0.93

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #71,069,960  ·  40 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x00000000…0002

0xb857c1…9be1

12 touches
15 conflicts

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0x4ab14837…e1b2

0x2a68ba…90c5

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x11f25e19…8bb1

0x34b655…2a6f

6 touches
3 conflicts

0x1d731f70…4557

0x34b655…2a6f

6 touches
3 conflicts

0x23114fac…630a

0x34b655…2a6f

6 touches
3 conflicts

0x3e1f7818…2fc8

0x34b655…2a6f

6 touches
3 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: 0xb857c13a…1a9be1

15 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity