← previous blocknext block →recent activity

Analyzing

Block #72,400,246

14 transactions · 12 stateful · 2026-05-04 15:08:52 UTC

Parallelism

71/100

Blocked

50%

Avg conflicts / tx

0.86

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #72,400,246  ·  14 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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…003d

0x065c9d…c394

8 touches
6 conflicts

0x24968e6d…0132

0x065c9d…c394

8 touches
6 conflicts

0xaf76e341…f696

0x065c9d…c394

4 touches
2 conflicts

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x5c32fddb…a788

0x065c9d…c394

4 touches
1 conflict

0xbbee74c2…567a

0x065c9d…c394

4 touches
1 conflict

0xf85d583e…b7da

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

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: 0x065c9d28…a9c394

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity