← previous blocknext block →recent activity

Analyzing

Block #72,977,469

17 transactions · 14 stateful · 2026-05-07 07:14:34 UTC

Parallelism

53/100

Blocked

57%

Avg conflicts / tx

1.53

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #72,977,469  ·  17 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x35b85d8e…1edd

0x34b655…2a6f

12 touches
15 conflicts

0xac2a0273…721b

0x34b655…2a6f

10 touches
10 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x71215888…8a72

0x34b655…2a6f

6 touches
3 conflicts

0x736c5b69…fb3f

0x34b655…2a6f

6 touches
3 conflicts

0x94710b77…a921

0x34b655…2a6f

6 touches
3 conflicts

0x9e96d5eb…aed9

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

15 conflicts on slot 0x35b85d8e2a…641edd

← previous block·next block →recent activity