← previous blocknext block →recent activity

Analyzing

Block #72,572,341

42 transactions · 29 stateful · 2026-05-05 10:14:54 UTC

Parallelism

83/100

Blocked

59%

Avg conflicts / tx

0.9

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #72,572,341  ·  42 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x60f7fbaf…bd58

0x34b655…2a6f

12 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0xbbee74c2…567a

0x065c9d…c394

8 touches
6 conflicts

0x8a35acfb…d1ad

0x8d66a4…3095

8 touches
6 conflicts

0x24968e6d…0132

0x065c9d…c394

8 touches
6 conflicts

0xbad68552…e6bf

0x34b655…2a6f

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x8a35acfb…d1ac

0x8d66a4…3095

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 0x60f7fbaf90…97bd58

← previous block·next block →recent activity