← previous blocknext block →recent activity

Analyzing

Block #72,284,174

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

Parallelism

58/100

Blocked

33%

Avg conflicts / tx

1.08

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,284,174  ·  12 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x24968e6d…0132

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0x28323c77…66af

0x065c9d…c394

4 touches
1 conflict

0x2417b8a2…ca2a

0x065c9d…c394

3 touches
1 conflict

0x0c1ca030…b61c

0x065c9d…c394

3 touches
1 conflict

0x0b428aae…6bfa

0x065c9d…c394

3 touches
1 conflict

0xe227487a…29c5

0x065c9d…c394

3 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 0x24968e6db4…f00132

← previous block·next block →recent activity