← previous blocknext block →recent activity

Analyzing

Block #71,416,533

30 transactions · 28 stateful · 2026-04-30 01:47:00 UTC

Parallelism

80/100

Blocked

61%

Avg conflicts / tx

1.57

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #71,416,533  ·  30 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

0x676f9f01…a8ac

0x34b655…2a6f

12 touches
15 conflicts

0xec3aaa61…4a8d

0x34b655…2a6f

10 touches
10 conflicts

0x998b43a7…00da

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0x2877f440…c2c8

0x34b655…2a6f

8 touches
6 conflicts

0x7862fbce…d1a5

0x34b655…2a6f

8 touches
6 conflicts

0x6af306bb…2e81

0x3bd359…433a

8 touches
6 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: 0x34b6552d…112a6f

15 conflicts on slot 0x676f9f01ee…dea8ac

← previous block·next block →recent activity